[sqlalchemy] Re: Ascii codec instead of unicode ? - Arun Kumar PG - com.googlegroups.sqlalchemy

16 messages in com.googlegroups.sqlalchemy[sqlalchemy] Re: Ascii codec instead ...

From	Sent On	Attachments
Arun Kumar PG	15 Aug 2007 08:33
jason kirtland	15 Aug 2007 08:44
Arun Kumar PG	15 Aug 2007 09:01
Michael Bayer	15 Aug 2007 10:17
Arun Kumar PG	15 Aug 2007 10:56
Arun Kumar PG	15 Aug 2007 10:57
Andrew Stromnov	15 Aug 2007 11:17
jason kirtland	15 Aug 2007 11:23
Arun Kumar PG	15 Aug 2007 11:32
jason kirtland	15 Aug 2007 11:36
Arun Kumar PG	16 Aug 2007 03:04
Arun Kumar PG	19 Aug 2007 02:22
jason kirtland	19 Aug 2007 09:28
Arun Kumar PG	20 Aug 2007 00:35
jason kirtland	20 Aug 2007 11:18
Arun Kumar PG	21 Aug 2007 00:32

Subject:	[sqlalchemy] Re: Ascii codec instead of unicode ?
From:	Arun Kumar PG (arun...@gmail.com)
Date:	08/19/2007 02:22:30 AM
List:	com.googlegroups.sqlalchemy

why do we want to say use_unicode=0 instead or use_unicode=True here?

On 8/16/07, jason kirtland <je...@discorporate.us> 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.

- A