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 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.
