| From: | Daniele Varrazzo <daniele(dot)varrazzo(at)gmail(dot)com> |
|---|---|
| To: | "psycopg(at)postgresql(dot)org" <psycopg(at)postgresql(dot)org> |
| Subject: | Re: psycopg2.Error.pgerror encoding ? |
| Date: | 2013-11-13 10:26:30 |
| Message-ID: | CA+mi_8acZsFSswM3w1m7B7pMY5xhtc34tuAbD0v80Mec-yjq_g@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | psycopg |
On Wed, Nov 13, 2013 at 1:52 AM, Karsten Hilbert
<Karsten(dot)Hilbert(at)gmx(dot)net> 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 Python 3 it is unicode decoded with the connection encoding (with
"replace" error handling, because we trust the database, yet we don't
want to die if things have gone really awry).
-- Daniele
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Karsten Hilbert | 2013-11-13 12:47:06 | Re: psycopg2.Error.pgerror encoding ? |
| Previous Message | Karsten Hilbert | 2013-11-13 01:52:04 | psycopg2.Error.pgerror encoding ? |