On Oct 8, 2008, at 8:54 PM, jason kirtland wrote:
> > Most likely you just need to configure the db-api's client encoding by > adding ?charset=utf8 onto your connection URL. > > Enough folks have hit this recently that I'm (again) considering > passing > through the engine encoding= parameter to the MySQLdb connection > setup. > I've resisted the urge for a while because we don't to my knowledge > re-configure any db-apis in any of the backends. But this keeps > coming > up despite being documented in the mysql section of the docs, and last > time I traced through it, it seemed like MySQLdb was ignoring the > server's configured connection_encoding so a little assist from the SA > side would probably be useful. > > I'll look at sneaking that into the upcoming rc2 unless the > implementation is untenable for some reason or there's an outcry. since im a total dumdum, why have i never had this issue in my own dealings with MySQL and Unicode ? I use the Unicode type, i dont use any charset= on my URL, and things work fine, including all of our unit tests. Is it actually storing the data incorrectly and we just see the same info at the SQLA round trip level ? --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
