On Sep 25, 2008, at 2:19 AM, Shawn Church wrote: > > > On Wed, Sep 24, 2008 at 11:04 PM, jason kirtland > <[EMAIL PROTECTED]> wrote: > > Shawn Church wrote: > > > > > > On Wed, Sep 24, 2008 at 10:45 PM, jason kirtland > <[EMAIL PROTECTED] > > <mailto:[EMAIL PROTECTED]>> wrote: > > > > > > Adding ?charset=utf8&use_unicode=1 to your MySQL connection > URL is a > > much easier way to get Unicode back from all DB access. > > > > > > Ok, that works. I thought that "create_engine(uri, encoding = > "latin1", > > convert_unicode = True) would do this. I am guessing from this > that the > > create_engine arguments are NOT being passed along to the dbapi > connector? > > No. I believe both of those are specifying the treatment of string > data > going _to_ the DB-API only, not bidirectional behavior. > > OK, lets see, check database encoding, table encoding, column > encoding, connection encoding/convert to unicode, sqlalchemy > encoding/convert to unicode, and client encoding and if they all > match up I should be good to go :-) Please don't take that as a > criticism of SQLAlchemy which is an excellent package it just always > amazes me how a simple (YES Unicode is SIMPLE) idea can get so > complicated.
use sqlite, and everything is unicode instantly ;) --~--~---------~--~----~------------~-------~--~----~ 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 [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/sqlalchemy?hl=en -~----------~----~----~----~------~----~------~--~---
