2010/6/9 Michael Bayer <[email protected]>: > 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.
That could be the key problem, yes! > 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. #2 (a or b) could also result on #3 - if some stuff fails, use the non-odbc approach. I'm away from the server right now, I'll do more tests tomorrow, and send you the results. I'm willing to open tickets and test more results, I'd love to see this solved for good. Again thank you for your time and answers. -- nosklo -- 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.
