thanks - I use pyodbc 2.1.11 with sqlalchemy 0.7.3
would upgrading one of them (or both) help me solve this? I saw in
sqlalchemy 0.7.7 changlog :
[feature] Added interim create_engine flag
supports_unicode_binds to PyODBC dialect,
to force whether or not the dialect
passes Python
freetds or windows ? critical
plus: stack trace? critical
On Aug 31, 2012, at 9:28 AM, alonn wrote:
thanks - I use pyodbc 2.1.11 with sqlalchemy 0.7.3
would upgrading one of them (or both) help me solve this? I saw in sqlalchemy
0.7.7 changlog :
[feature] Added interim
I'm working on windows 7, where can I find the stack trace?
On Friday, August 31, 2012 4:53:15 PM UTC+3, Michael Bayer wrote:
freetds or windows ? critical
plus: stack trace? critical
On Aug 31, 2012, at 9:28 AM, alonn wrote:
thanks - I use pyodbc 2.1.11 with sqlalchemy 0.7.3
when it says UnicodeDecodeError, there should be a big stack trace.
Since I don't know from your description what feature is actually failing to
decode. I don't understand how a code change in a client of the result set
could workaround such an issue if the decoding issue is on the result
some of my sqlalchemy 0.7.3 (with tubrogears 2.1.4) models work with a
mssql 2005 db using pyodbc.
(No can't change this, don't bother suggesting, this is an enterprise
financial system, I can just read and write to certain tables there)
the query returned are encoded windows-1255 instead of
what ODBC driver ? the encoding issues are typically configured with ODBC.
it's a huge difference if you're on the windows drivers, vs. freetds, vs
anything else.
also I use MSSQL 2005 in production financial applications as well.
On Aug 28, 2012, at 4:43 PM, alonn wrote:
some of my
