On Tuesday 23 October 2007 00:58:02 Lukasz Szybalski wrote:
> UnicodeDecodeError: 'utf8' codec can't decode byte 0xbf in position
> 261: unexpected code byte
> or
> raise exceptions.DBAPIError("Connection failed", e)
> sqlalchemy.exceptions.DBAPIError: (Connection failed) (TypeError)
> 'convert_unicode' is an invalid keyword argument for this function
>
> On 10/22/07, Christoph Zwerschke <[EMAIL PROTECTED]> wrote:
> > Lukasz Szybalski wrote:
> > > Are these the same or are they different? If they are different what
> > > is the argument set I can use?
> >
> > I guess the difference is that "use_unicode" is an option that is
> > evaluated by the mysqldb DBAPI adapter,
>
> Is there a list of available options for that somewhere on turbogears?
>
> while convert_unicode is an
>
> > option that is evaluated by SQLAlchemy. So the latter must probably not
> > be included in the URL, but needs to be passed as an additional
> > parameter to create_engine.
>
> Where would be a place to put these options in? Which config file?
> What would be the proper line.
>
> I partially solved this issue by adding charset=ascii to the dbi.uri
> sqlalchemy.dburi="mysql://user:[EMAIL PROTECTED]:3306/dbname?charset=ascii"
>
> Not sure how to solve this if I wanted to support utf8/unicode ? !
You certainly didn't "solve" anything. All you did was to tell MySQL do
convert all data delivered using the ascii-codec, losing all foreign
characters. I wouldn't call that a solution.
The overall problem is a SA-one. You might be better off looking there for
help.
Diez
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"TurboGears" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/turbogears?hl=en
-~----------~----~----~----~------~----~------~--~---
