seems like convert_unicode=True (or Unicode type) is already happening there. its not going to play well with MySQL client encoding if you have "use_unicode=1" turned on in my.cnf or on MySQLDB.
On Jul 25, 2007, at 9:12 AM, Arun Kumar PG wrote: > the stack trace is as follows: > > File "/aab/sqlalchemy/orm/query.py", > line 331, in instances > File "/aab/sqlalchemy/orm/mapper.py", > line 1201, in _instance > File "/aab/sqlalchemy/orm/mapper.py", > line 1236, in populate_instance > File "/aab/sqlalchemy/orm/interfaces.py", > line 77, in execute > File "/aab/sqlalchemy/orm/strategies.py", > line 39, in process_row > File "/aab/sqlalchemy/engine/base.py", > line 725, in __getitem__ > File "/aab/sqlalchemy/engine/base.py", > line 632, in _get_col > File "/aab/sqlalchemy/types.py", > line 178, in convert_result_value > File "/usr/lib/python2.4/encodings/utf_8.py", line 16, in decode > return codecs.utf_8_decode(input, errors, True) > UnicodeDecodeError: 'utf8' codec can't decode bytes in position 94-96: > invalid data > > > > On 7/25/07, Arun Kumar PG <[EMAIL PROTECTED]> wrote: > Guys, > > I am getting this error on reading data from a MySQL table. I have > specified the charset of the table as utf-8 and collation > utf8_general_ci. Do I need to do anything else ? Will > convert_unicode=True help? > > -- > Cheers, > > - A > > > > -- > 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 -~----------~----~----~----~------~----~------~--~---
