Michael, thanks for your answer. 2010/6/8 Michael Bayer <[email protected]>: > On Jun 8, 2010, at 5:38 PM, Clovis Fabricio wrote: >> I'm aware that sqlalchemy 2005 has the DATE type, but sqlalchemy 2000 >> doesn't. > according to our source, DATE is only available on 2008, not 2005 or 2000. > I'm not 100% sure that is correct.
True. Sorry for the misinformation. > tell me what this test produces: Weird results: > engine = create_engine( > 'mssql+pyodbc://sa:s...@myserver/mydb?driver=FreeTDS') > engine.connect() > print engine.dialect.server_version_info (95, 8, 255) (Now what that means, exactly?) > and also what happens if you force it: > engine = create_engine(...) > engine.connect() > engine.dialect.server_version_info = (8,) That works fine. If I manually set the server_version_info to (8,) the rest of the code works as expected. So it seems the problem is in version detection code. I did one more test to help identify where the problem is: print engine.connect().connection.connection.getinfo(pyodbc.SQL_DBMS_VER) returns 95.08.0255 Anybody has any clue on why it does that? Is that expected? Thanks in advance, -- You received this message because you are subscribed to the Google Groups "sqlalchemy" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/sqlalchemy?hl=en.
