Thank you.
Switching to 1.2.2 and using connect_args = {'use_unicode':
False,'charset': 'utf8'} works fine for me.
Jürgen
Michael Bayer schrieb:
> I believe this is the ticket:
>
> http://sourceforge.net/tracker/index.php?func=detail&aid=1592353&group_id=22307&atid=374932
>
> its a little ambiguous as to its resolution, maybe I'll ask Shannon
> what his most recent experiences were.
>
>
> On Sep 17, 2008, at 12:03 PM, Bo Shi wrote:
>
>
>> While researching which version to deploy, I had run into a thread
>> post _claiming_ that 1.2.2 had a critical bug which was documented in
>> the fedora bugzilla. I never managed to actually find said bug but it
>> scared me off. The reason we went with 1.2.1p2 was because it was the
>> version the Django people have been using with success.
>>
>> At any rate, the workaround I posted seems to work for us thus far,
>> though I don't have a good understanding of exactly why it works (I
>> suspect it tiptoes around a double-encoding bug in mysqldb).
>>
>>
>> Bo
>>
>> On Wed, Sep 17, 2008 at 11:31 AM, Michael Bayer
>> <[EMAIL PROTECTED]> wrote:
>>
>>> On Sep 17, 2008, at 10:50 AM, Bo Shi wrote:
>>>
>>>
>>>> I ran into a similar issue using MySQL-python-1.2.1_p2-1 (mysqldb)
>>>> with SA 0.4.2p3-1.
>>>>
>>> I would advise upgrading to MySQL-python 1.2.2. I believe some utf-8
>>> issues have been fixed.
>>>
>>>
>>>
>
>
> >
>
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---
