On Sep 8, 2011, at 11:37 AM, Victor Olex wrote: > Pyodbc issue 209 works fine in my setup.
that is very strange ? There are files missing from the .zip. If you installed from the zip I don't see how it built for you. Here's the original issue: http://code.google.com/p/pyodbc/issues/detail?id=192 > I think the key thing is > matching SQL Server version with the correct TDS protocol version and > correct FreeTDS version. I use tds version 8.0 for this particular DSN and that is working fine in production with FreeTDS 0.82, on both linux and OSX platforms. These issues have all been introduced with FreeTDS 0.91. Here, I tried 7.2 and got slightly better results, though unicode round trips still fail when Python unicodes are passed. PyODBC still dies with "MemoryError" if I attempt to query for a table that already exists. > Also with regards to your Mac testing, check > if you have the libiconv installed and that FreeTDS is built with it. > http://www.freetds.org/userguide/config.htm yup that's in my configure: checking for iconv... yes checking how to link with libiconv... -liconv checking for iconv declaration... install-shextern size_t iconv (iconv_t cd, char * *inbuf, size_t *inbytesleft, char * *outbuf, size_t *outbytesleft); > > On Sep 8, 10:32 am, Michael Bayer <mike...@zzzcomputing.com> wrote: >> On Sep 8, 2011, at 9:37 AM, Victor Olex wrote: >> >>> I never for a moment thought that your change was thoughtless. To the >>> contrary, I have huge respect for SQLAlchemy. I will try to test the >>> drop_all and your pyodbc issue with my setup and to report here later >>> today. >> >> thanks ! Unfortunately I've tested this some more and things are looking >> very, very bad. For us to support 0.91, we'd need to figure out how to >> get all of our "table exists" functions to work. If you look >> athttp://www.sqlalchemy.org/trac/ticket/2273, I've now added a patch that >> detects 0.82 vs. 0.91 and sets the flag, but you can see that we can't send >> u'' strings when we query INFORMATION_SCHEMA still - literally, the number >> of characters present in one of the bind parameters changes the behavior. >> So there is something very strange and arbitrary (seems basically like it's >> just making guesses about datatypes) going on with the internals of FreeTDS, >> and I'm not optimistic about being able to get clear answers from their >> list. >> >> Would you have any resources to evaluate the test cases on that ticket , >> both are now against pure PyODBC 2.1.9? Without being able to query >> information schema, none of our unit tests can run period with 0.91 - I need >> a reliable way to do so, hopefully without losing support for table names >> that contain non-ascii characters. A lot of adjustments to the MSSQL >> dialect and testing will be needed. > > -- > 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. > -- 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.
