- ResultProxy and friends always reference the DBAPI connection at the same time

as the cursor.  There is no reason for CursorFairy - the only use case would be,
end-user is using the pool or pool.manage with DBAPI connections, uses a cursor,
deferences the owning connection and continues using cursor.  This is an almost
nonexistent use case and isn't correct usage at a DBAPI level.  Take out CursorFairy.
- move the "check for a dot in the colname" logic out to the sqlite dialect.

1 files changed, 3 insertions, 1 deletions

diff --git a/test/sql/test_quote.py b/test/sql/test_quote.py
index 8f27a7b3c..e880388d7 100644
--- a/test/sql/test_quote.py
+++ b/test/sql/test_quote.py
@@ -140,7 +140,9 @@ class QuoteTest(TestBase, AssertsCompiledSQL):
         if labels arent quoted, a query in postgresql in particular will fail since it produces:
 
         SELECT LaLa.lowercase, LaLa."UPPERCASE", LaLa."MixedCase", LaLa."ASC"
-        FROM (SELECT DISTINCT "WorstCase1".lowercase AS lowercase, "WorstCase1"."UPPERCASE" AS UPPERCASE, "WorstCase1"."MixedCase" AS MixedCase, "WorstCase1"."ASC" AS ASC \nFROM "WorstCase1") AS LaLa
+        FROM (SELECT DISTINCT "WorstCase1".lowercase AS lowercase, 
+                "WorstCase1"."UPPERCASE" AS UPPERCASE, 
+                "WorstCase1"."MixedCase" AS MixedCase, "WorstCase1"."ASC" AS ASC \nFROM "WorstCase1") AS LaLa
 
         where the "UPPERCASE" column of "LaLa" doesnt exist.
         """