I'm not sure of the mechanics of what you're experiencing, but make
sure you use charset=utf8&use_unicode=0 with MySQL.
On Dec 5, 2008, at 4:17 PM, n00b wrote:
>
> greetings,
>
> SA (0.5.0rc1) keeps returning utf hex in stead of utf-8 and in the
> process driving me batty. all the mysql setup is fine, the chars look
> good and are umlauting to goethe's delight. moreover, insert and
> select are working perfectly with the MySQLdb api on three different
> *nix systems, two servers, ... it works.
>
> where things fall apart is on the retrieval side of SA; inserts are
> fine (using the config_args = {'charset':'utf8'} dict in the
> create_engine call).
>
> for example, ë, the latin small letter e with diaeresis, is stored in
> mysql hex as C3 AB; using the MySQldb client, this is exactly what i
> get back: '\xc3\xab' (in the # -*- coding: UTF-8 -*- environment) no
> further codecs work required. SA, on the other hand, hands me back the
> utf-hex representation, '\xeb'.
>
> there must be some setting that i'm missing that'll give the
> appropriate utf-8 representation at the SA (api) level. any ideas,
> suggestions?
>
> thx
>
> yes, i could do '\xeb'.encode('utf8) but it's not an option. we got
> too much data to deal with and MySQLdb is working perfectly well
> without the extra step. thx.
>
> >
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---
