You should put this into your .freetds.conf file to ensure that FreeTDS will tell iconv to do the right thing (my understanding is that all unicode data is encoded to UCS-2 by FreeTDS)
tds version = 8.0 client charset = UTF-8 SQL Alchemy create_engine has an encoding kwarg: encoding=’utf-8’ – the encoding to use for all Unicode translations, both by engine-wide unicode conversion as well as the Unicode type object This should be set to the same value as you have for 'client charset' in the .freetds.conf file. You can run into problems when bogus data has been stuff into the nvarchar field at the dataserver as it will cause the python codec to blow up when retrieving the data so "Don't Do That" (I discovered this the hard way by having a server-side job that was populating the data and not ensuring that the encoding was well-formed) pjjH --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
