From: | Frank Kauff <fkauff(at)biologie(dot)uni-kl(dot)de> |
---|---|
To: | psycopg(at)postgresql(dot)org |
Subject: | Error: no Python Codec for client encoding |
Date: | 2011-10-19 15:41:36 |
Message-ID: | 4E9EEFB0.1030601@biologie.uni-kl.de |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | psycopg |
Nobody with any ideas what the problem could be? Any help would be
greatly appreciated.
Frank
On 10/18/2011 02:08 PM, Frank Kauff wrote:
> Hi all,
>
> I'm trying to run psycopg2-2.4.2 ZPsychopgDA with Zopw 2.13.8.
> However, when I try to add the adapter to my zope site and enter the
> connection string etc., I get the Zope error below. Any idea what
> could be the reason? Some other versions of psycopg2 I tried give the
> same error
>
> Thanks,
> Frank
>
>
>
> Zope Error
>
> Zope has encountered an error while publishing this resource.
>
> Error Type: OperationalError
> Error Value: no Python codec for client encoding ''
>
> Traceback (innermost last):
>
> Module ZPublisher.Publish, line 126, in publish
> Module ZPublisher.mapply, line 77, in mapply
> Module ZPublisher.Publish, line 46, in call_object
> Module Products.ZPsycopgDA.DA, line 61, in
> manage_addZPsycopgConnection
> Module Products.ZPsycopgDA.DA, line 81, in __init__
> Module Products.ZPsycopgDA.DA, line 96, in edit
> Module Products.ZPsycopgDA.DA, line 127, in connect
> Module Products.ZPsycopgDA.db, line 85, in open
> Module Products.ZPsycopgDA.db, line 50, in getconn
>
> OperationalError: no Python codec for client encoding ''
From | Date | Subject | |
---|---|---|---|
Next Message | Mark Theisen | 2011-10-19 15:45:59 | Re: connection already closed error |
Previous Message | Marko Kreen | 2011-10-19 15:13:28 | Re: Rollback on close [Was: Fwd: [DB-SIG] conn.close() idempotence] |