From: | "Frank Kauff" <fkauff(at)biologie(dot)uni-kl(dot)de> |
---|---|
To: | "Daniele Varrazzo" <daniele(dot)varrazzo(at)gmail(dot)com> |
Cc: | <psycopg(at)postgresql(dot)org> |
Subject: | Re: Error: no Python Codec for client encoding |
Date: | 2011-10-19 16:59:42 |
Message-ID: | web-87385945@uni-kl.de |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | psycopg |
Hi Daniele,
it's a standard Zope installation and a psycopg
installation out of the box - so I didn't change any
configuration. How can i configure it so that is no longer
an empty string?
Frank
On Wed, 19 Oct 2011 17:27:12 +0100
Daniele Varrazzo <daniele(dot)varrazzo(at)gmail(dot)com> wrote:
> On Wed, Oct 19, 2011 at 4:41 PM, Frank Kauff
><fkauff(at)biologie(dot)uni-kl(dot)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(at)postgresql(dot)org)
> To make changes to your subscription:
> http://www.postgresql.org/mailpref/psycopg
--
From | Date | Subject | |
---|---|---|---|
Next Message | Daniele Varrazzo | 2011-10-19 17:08:02 | Re: Error: no Python Codec for client encoding |
Previous Message | Daniele Varrazzo | 2011-10-19 16:27:12 | Re: Error: no Python Codec for client encoding |