Hello. Thank you for the information. I am using freetds 0.91 without issues. But note that on Debian/testing, the driver file libtdsodbc.so is NOT part of any freetds-* package. It is part of the package tdsodbc. See my previous e-mail for detailed installation instructions.
Ladislav Lenart On 10.10.2012 17:17, Michael Bayer wrote: > > On Oct 10, 2012, at 6:01 AM, Ladislav Lenart wrote: > >> Hello Michael. >> >> Just a question. When I first posted about my problem of how to connect to >> MSSQL >> from Linux/Debian, you mentioned that you are running similar setup in >> production, or at least that is how I understood it. Am I correct? If so, is >> it >> similar to this: >> * Connect from Linux/Debian >> * To MSSQL >> * Via pyodbc >> * using freetds >> ? >> >> Are there some differences? > > Production is CentOs but otherwise that's what we do, yup. I also can run > unicode-aware tests against a SQL Server instance from a local fedora > instance as well as OSX. > > I will note that we have stayed on FreeTDS 0.82 as opposed to 0.91. I have > tested 0.91 on linux and we've repaired some issues for people using 0.91, > however from OSX there are 0.91 unicode issues I haven't been able to > overcome. We've kept our CentOS production environment on 0.82 as well > just because it already works. -- You received this message because you are subscribed to the Google Groups "sqlalchemy" group. To post to this group, send email to sqlalchemy@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.
