Yes. it's being done. I create the engine and then set convert unicode =
True.

On 8/15/07, Michael Bayer <[EMAIL PROTECTED]> wrote:
>
> are you using convert_unicode=True and/or the Unicode type ?
> On Aug 15, 2007, at 12:01 PM, Arun Kumar PG wrote:
>
> All tables are having a charset of utf8. Additionally, I am issuing SET
> NAMES 'utf8' statement as a part of connection establishment.
>
> Anything that is wrong here or missing ?
>
> On 8/15/07, jason kirtland <[EMAIL PROTECTED]> wrote:
> >
> >
> > Arun Kumar PG wrote:
> > > Hi All,
> > >
> > > Recently I upgraded to the version 3.9 of SA. Post that whenever I am
> > > trying to save characters in different language in the table I am
> > > getting the below exception:
> > >
> > > File "/src/sqlalchemy/engine/base.py",
> > > line 601, in _execute
> > > raise exceptions.SQLError(context.statement, context.parameters, e)
> > > SQLError: (UnicodeDecodeError) 'ascii' codec can't decode byte 0xc3 in
> >
> > > position 1: ordinal not in range(128)
> > >
> > > I am wondering why it is using ascii codec instead of unicode ?
> > >
> > > FYI: I am using MySQL 4.1 and the charset of table is utf-8.
> >
> > Odd to see ascii there instead of latin1. Is your database configured
> > for utf-8 client connections?
> >
> >
> >
>
>
> --
> 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
-~----------~----~----~----~------~----~------~--~---

Reply via email to