On Jun 9, 2010, at 6:54 PM, Clovis Fabricio wrote: > 2010/6/9 Michael Bayer <[email protected]>: >> OK, here's something else to try, this would help with the pyodbc issue in >> any case. Turn on ODBC logging (its a setting with your ODBC driver). You >> should get a dumpfile like the one here: >> http://www.egenix.com/mailman-archives/egenix-users/2008-November/114471.html > > I turned on unixodbc tracing by following this procedure: > > http://www.easysoft.com/support/kb/kb00945.html > > By doing that, I got a very different trace file from the one on your > link. The relevant part is:
I think I know what the problem is. You need to use freetds version 7.0 or 8.0. If I set mine down to "4.2", I get your goofy results. There's actions we can take here. 1. document that freetds version 7, 8 be used 2. have the MS-SQL pyodbc + mxodbc dialects dump out a warning if we detect freetds version under 7 (or perhaps, if we see an odd result for this value) 3. still use the non-odbc approach to get this particular value I sort of like #2 for the time being. Though I am not seeing any way to get the protocol version of FreeTDS from the connection, suggesting #1 (or #2b). If theres legit reasons people need to be on 4.2, we can look into #3. -- 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.
