Re: Character Encoding Question

From: Daniele Varrazzo <daniele(dot)varrazzo(at)gmail(dot)com>
To: Don Parris <parrisdc(at)gmail(dot)com>
Cc: psycopg(at)postgresql(dot)org
Subject: Re: Character Encoding Question
Date: 2013-03-28 16:41:30
Message-ID: CA+mi_8Y=v7jZ2Pjq=-C3f5QqX0qbRFoaeWsAJFEcBMD9VFrSdQ@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: psycopg

On Thu, Mar 28, 2013 at 4:34 PM, Don Parris <parrisdc(at)gmail(dot)com> wrote:
> Thanks Daniele,
>
> I'm using psycopg 2.4.5 with Python 3.2.3 on Kubuntu 12.10.
>
> This is the connection encoding based on a quick check at the Python
> console:
>>>>print(con.encoding)
> SQLASCII

In this case it's natural that you get an error on decode. But is it
really the database encoding? What does this query say:

cur = con.cursor()
cur.execute("show client_encoding")
print cur.fetchone()[0]

> I honestly don't know where the error actually is - not a very advanced
> programmer by any means. All I really know is that the program breaks when
> I use fetchall(), but it works with fetchone() and fetchmany(). It could
> have something to do with the way my main program module imports the module
> that calls the function, for all I know. Here is the traceback:

I'll try to load your dataset and play with it, thank you.

-- Daniele

In response to

Responses

Browse psycopg by date

  From Date Subject
Next Message Federico Di Gregorio 2013-03-28 17:12:11 Re: Character Encoding Question
Previous Message Don Parris 2013-03-28 16:34:43 Re: Character Encoding Question