Re: Character Encoding Question
От | Don Parris |
---|---|
Тема | Re: Character Encoding Question |
Дата | |
Msg-id | CAJ-7yonccxZTKRdAc_f4GPp2Znk1aBnfyHzb+xQCrwi_Xeu1aQ@mail.gmail.com обсуждение исходный текст |
Ответ на | Re: Character Encoding Question (Daniele Varrazzo <daniele.varrazzo@gmail.com>) |
Список | psycopg |
For the list:
Here is the result of the query you suggested:
>>> cur = con.cursor()
>>> cur.execute("show client_encoding")
>>> print(cur.fetchone()[0])
SQL_ASCII
I created the DB in postgresql using the following command:Here is the result of the query you suggested:
>>> cur = con.cursor()
>>> cur.execute("show client_encoding")
SQL_ASCII
CREATE DATABASE mydb
WITH TEMPLATE template0 ENCODING 'UTF8';
On Thu, Mar 28, 2013 at 12:41 PM, Daniele Varrazzo <daniele.varrazzo@gmail.com> wrote:
On Thu, Mar 28, 2013 at 4:34 PM, Don Parris <parrisdc@gmail.com> wrote:In this case it's natural that you get an error on decode. But is it
> 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
really the database encoding? What does this query say:
cur = con.cursor()
cur.execute("show client_encoding")
print cur.fetchone()[0]I'll try to load your dataset and play with it, thank you.
> 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:
-- Daniele
--
D.C. Parris, FMP, Linux+, ESL Certificate
Minister, Security/FM Coordinator, Free Software Advocate
GPG Key ID: F5E179BE
В списке psycopg по дате отправления: