From: | Karsten Hilbert <Karsten(dot)Hilbert(at)gmx(dot)net> |
---|---|
To: | psycopg(at)postgresql(dot)org |
Subject: | Re: psycopg2.Error.pgerror encoding ? |
Date: | 2013-11-13 12:47:06 |
Message-ID: | 20131113124706.GD4767@hermes.hilbert.loc |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | psycopg |
On Wed, Nov 13, 2013 at 10:26:30AM +0000, Daniele Varrazzo wrote:
> > I have a simple (?) question regarding psycopg2.Error
> >
> > http://initd.org/psycopg/docs/module.html#exceptions
> >
> > Which encoding is the string attribute .pgerror
> > going to be in ?
>
> In Python 2 it will be in the connection encoding; specifically we
> receive the 8-bit message from the backend and we just create a Python
> string out of that data, without re-checking the data is valid in that
> encoding (we trust the database).
In other words:
unicode(exception.pgerror, exception.cursor.connection.encoding, 'replace')
"should" do the "right" thing ?
Karsten
--
GPG key ID E4071346 @ gpg-keyserver.de
E167 67FD A291 2BEA 73BD 4537 78B9 A9F9 E407 1346
From | Date | Subject | |
---|---|---|---|
Next Message | Daniele Varrazzo | 2013-11-13 14:39:35 | Re: psycopg2.Error.pgerror encoding ? |
Previous Message | Daniele Varrazzo | 2013-11-13 10:26:30 | Re: psycopg2.Error.pgerror encoding ? |