I think I can help reproduce this, but one has to configure the base system
in a non C or english locale.
E.g. the system I work with is in french: it's default locale is
fr_FR.UTF-8, hence the postgresql server
I installed on it runs with that locale too, by default. One can check with
the
Sorry to ressurrect this thread but the problem is still there. Since
SQLAlchemy knows the encoding used to communicate with the database, it can
properly decode the error strings returned by the database to unicode. So,
I think it should be SQLAlchemy's responsibility to convert the error
OK as I said earlier, I'm not able to reproduce this.So I'd need that
reproduction case in order to do anything. To be honest it sounds more like a
psycopg2 bug, since psycopg2 does the decoding in most cases nowadays and even
works with Python 3, so for it to be raising an exception with
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
