Re: Error: no Python Codec for client encoding

Поиск
Список
Период
Сортировка
От Frank Kauff
Тема Re: Error: no Python Codec for client encoding
Дата
Msg-id web-87389413@uni-kl.de
обсуждение исходный текст
Ответ на Re: Error: no Python Codec for client encoding  (Daniele Varrazzo <daniele.varrazzo@gmail.com>)
Список psycopg
I changed the code from

    conn.set_client_encoding(self.encoding)

to

    conn.set_client_encoding('utf-8')

which seems, according to the code, to be the default (but
somehow wasn't?),

and the connection works.

(Other erros pop up, but might be not related to psycopg)

Thanks for the help!
Frank


On Wed, 19 Oct 2011 17:27:12 +0100
  Daniele Varrazzo <daniele.varrazzo@gmail.com> wrote:
> On Wed, Oct 19, 2011 at 4:41 PM, Frank Kauff
><fkauff@biologie.uni-kl.de> wrote:
>
>>>    Module Products.ZPsycopgDA.db, line 50, in getconn
>
> This line only does
>
>    conn.set_client_encoding(self.encoding)
>
> and self.encoding is passed to the DB constructor. It is
>configured to
> be an empty string, which we don't like. Where does this
>empty string
> come from? I suspect misconfiguration.
>
> -- Daniele
>
> --
> Sent via psycopg mailing list (psycopg@postgresql.org)
> To make changes to your subscription:
> http://www.postgresql.org/mailpref/psycopg

В списке psycopg по дате отправления:

Предыдущее
От: Daniele Varrazzo
Дата:
Сообщение: Re: Rollback on close [Was: Fwd: [DB-SIG] conn.close() idempotence]
Следующее
От: Federico Di Gregorio
Дата:
Сообщение: Re: Error: no Python Codec for client encoding