Whooops. the problem in coming on the box which is running mysqldb1.2.0. Actually it's a non-upgraded server with mysqldb 1.2.0. I was looking at the code on my box which contains 1.2.2.
But I am sure that even with mysqldb 1.2.0 the existing SA version was working fine. and that's why "init_command" is being used there as "charset" is not there in 1.2.0 as connect kwargs. Any clue? On 8/16/07, jason kirtland <[EMAIL PROTECTED]> wrote: > > > Ok you need to get tArun wrote: > > I am using mysqldb-1.2.2. I am passing 'SET NAMES' to connect > > method as a value for "init_command" parameter. All tables have > > utf8 charset. And I pass convert_unicode=True to engine. > > > > Let me know if anything else is required. > > Ok, you need to get that charset to the driver. Try removing SET > NAMES from your init_command, and instead pass charset=utf8 and > use_unicode=0 in your database connection URL. > > > > > > > -- Cheers, - A --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
