On Jun 9, 2010, at 6:06 PM, Clovis Fabricio wrote: > 2010/6/9 Michael Bayer <mike...@zzzcomputing.com>: >> ah well that's the problem. this detection code might be wrong for 2005, >> 2008 as well. >> If you want to try out this PyODBC code, perhaps we need to check with the >> pyodbc list: >> connection = pyodbc.connect(...) >> print connection.getinfo(pyodbc.SQL_DBMS_VER) > > Result: > 95.08.0255 > > Perhaps we could change the mssql dialect to always use Microsoft-documented > way of fetching version: > > http://support.microsoft.com/kb/321185 > > Instead of relying on pyodbc-specific function, all mssql connections > for any dbapi module could use it, since it is just a normal query. > > What do you think?
I would so much prefer pyodbc's method to work. if we cant figure anything out, then sure we don't have much option, but id want to poke on pyodbc's and maybe freetds' list in the next couple of days to see what we find. > > -- > nosklo > > -- > 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. > -- 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.
