- 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, 1 insertions, 1 deletions

diff --git a/lib/sqlalchemy/engine/default.py b/lib/sqlalchemy/engine/default.py
index 587dbf92f..6c708aa52 100644
--- a/lib/sqlalchemy/engine/default.py
+++ b/lib/sqlalchemy/engine/default.py
@@ -405,7 +405,7 @@ class DefaultExecutionContext(base.ExecutionContext):
             self.parameters = self.__encode_param_keys(parameters)
             self.executemany = len(parameters) > 1
             
-            if isinstance(statement, unicode) and not dialect.supports_unicode_statements:
+            if not dialect.supports_unicode_statements and isinstance(statement, unicode):
                 self.unicode_statement = statement
                 self.statement = statement.encode(self.dialect.encoding)
             else: