Re: Coding when open conection (+- Solved)

Il giorno ven, 10/03/2006 alle 19.35 +0100, Oswaldo Hernández ha
scritto:
[snip]
> I forced a conversion of the postgresql error string from latin1 to
> unicode and now works fine in  the connect moment and after of
> client_encoding.

I'm glad you solved it. I'd like to solve this in psycopg too but if
PostgreSQL let you use 2 different encodings (for messages and data) I
don't see any viable solution. :/

-- 
Federico Di Gregorio                         http://people.initd.org/fog
Debian GNU/Linux Developer                                
fog-8fiUuRrzOP0dnm+yROfE0A@xxxxxxxxxxxxxxxx
INIT.D Developer                                           
fog-NGVKUo/i/6DYtjvyW6yDsg@xxxxxxxxxxxxxxxx
  99.99999999999999999999% still isn't 100% but sometimes suffice. -- Me

signature.asc
Description: Questa parte del messaggio =?ISO-8859-1?Q?=E8?= firmata

_______________________________________________
Psycopg mailing list
Psycopg-IAPFreCvJWPBWskQ1e/+sw@xxxxxxxxxxxxxxxx
http://lists.initd.org/mailman/listinfo/psycopg