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 > 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 unicode literals to PyODBC > or not. > > *would using that solve my problem? how and where should I call that flag?* > > > > On Wednesday, August 29, 2012 12:55:50 AM UTC+3, Michael Bayer wrote: >> >> 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 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 utf-8 >> failing to return unicode causes various 'UnicodeDecodeError' error in >> sprox and toscawidgets which I can override manualy by rewriting certain >> lines in the sprox/tw.forms source code but not exactly an optimal solution >> >> is there a way to specify in the connection url to convert the data to >> standard unicode encoding? >> >> currently using the following format: >> >> sqlalchemy.second.url = mssql://user:password@SERVER\db >> >> or maybe changing some parameter in the sqlalchemy engine should do the >> trick? >> >> >> >> thanks for the help >> >> >> >> -- >> You received this message because you are subscribed to the Google Groups >> "sqlalchemy" group. >> To view this discussion on the web visit >> https://groups.google.com/d/msg/sqlalchemy/-/xTmE0yTs810J. >> To post to this group, send email to sqlal...@googlegroups.com. >> To unsubscribe from this group, send email to >> sqlalchemy+...@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 view this discussion on the web visit > https://groups.google.com/d/msg/sqlalchemy/-/mIe-QOn7JRgJ. > To post to this group, send email to sqlal...@googlegroups.com<javascript:> > . > To unsubscribe from this group, send email to > sqlalchemy+...@googlegroups.com <javascript:>. > 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 view this discussion on the web visit https://groups.google.com/d/msg/sqlalchemy/-/wwRZkYf0dFEJ. 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.
