On Mar 6, 2008, at 8:29 PM, Michael Bayer wrote:
>
>
> On Mar 6, 2008, at 6:35 PM, jean-philippe dutreve wrote:
>
>>
>> Hi all,
>>
>> I use SQLAlchemy-0.4.2p3, postgreSQL 8.2.4 (UTF8 configured) and
>> psycopg2.
>> I have no issue with unicode DATA in and out of the database.
>>
>> My problem is that when an IntegrityError is thrown, the exception
>> message is a string encoded in utf8.
>> And the logging module throws an UnicodeDecodeError.
>>
>> Is there a way that the exception message is type of unicode instead
>> of string?
>
>
> logging module itself throws UnicodeDecodeError ? are you sending
> exception messages using logging.debug() or similar ? my impression
> is that you'd want to decode those manually doing something like
> string.decode('utf-8').
of course my collegue suggests, "maybe we should decode exception
messages within SA using engine.encoding", *after* I push send....but
I want to make sure im understanding how you're getting it to raise
the error in the first place since we're not able to trip up logging
on this end.
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---
