Hello,
I had a custom dialect based on the PyODBC functionality that was
working with SQLA SVN-6738. Upgrading to beta 3, my tests no longer
pass, so I've begun the process updating - on_connect() was easy, now
I'm stumped on connect(...). I've gotten to the point where, when
using my dialect, connect() fails because it attempts to run
self.dbapi.connect(...) but the PyODBC connector seems to implement it
as a classmethod:
Taking the following from the connector in revision control:
9 class PyODBCConnector(Connector):
27 @classmethod
28 def dbapi(cls):
29 return __import__('pyodbc')
84 def initialize(self, connection):
85 # determine FreeTDS first. can't issue SQL easily
86 # without getting unicode_statements/binds set up.
87
88 pyodbc = self.dbapi
89
90 dbapi_con = connection.connection
91
92 self.freetds = bool(re.match(r".*libtdsodbc.*\.so",
dbapi_con.getinfo(pyodbc.SQL_DRIVER_NAME)))
If dbapi is implemented as a class method, then wouldn't the call on
line 92 fail? Indeed, that's what I'm seeing. So is self.dbapi
getting assigned somewhere else?
Thanks,
Bo
--
You received this message because you are subscribed to the Google Groups
"sqlalchemy" group.
To post to this group, send email to sqlalch...@googlegroups.com.
To unsubscribe from this group, send email to
sqlalchemy+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/sqlalchemy?hl=en.
