Re: getquoted and unicode - Mailing list psycopg

From Daniele Varrazzo
Subject Re: getquoted and unicode
Date
Msg-id AANLkTiketPhAv_nO4OrHHPxpzmGmE9UuqFjQgKiEaViH@mail.gmail.com
Whole thread Raw
In response to getquoted and unicode  ("Carl S. Yestrau Jr." <carl@featureblend.com>)
Responses Re: getquoted and unicode  ("Carl S. Yestrau Jr." <carl@featureblend.com>)
List psycopg
On Sun, Jan 23, 2011 at 7:53 AM, Carl S. Yestrau Jr.
<carl@featureblend.com> wrote:
> I'm currently using psycopg2.extensions.adapt without a connection
> intentionally.
>
> The following results in a: psycopg2.InterfaceError: can't encode
> unicode string to latin-1
>
> import psycopg2
>
> psycopg2.extensions.register_type(psycopg2.extensions.UNICODE)
> adapted = psycopg2.extensions.adapt(u'test')
> adapted.getquoted()

You are right, it should work, and it works indeed in the psycopg dev
version, but it looks broken in 2.3.2 and probably in previous
versions.

I can see that the glitch happens when the adapter is not "prepared"
for the connection: if you add that step it will work. Preparation
always happens when the parameters are passed to the query.

    >>>  cnn = psycopg2.connect('dbname=test')
    >>> adapted.prepare(cnn)
    >>> adapted.getquoted()
    "E'test'"

Preparation is probably not mentioned in the docs at all: this is
something else to review. If you are into writing an adapter, you may
want to take a look to SQL_IN or the hstore adapter for complete
examples.

If you need to work without the connection, do you want to try
checking out my dev branch? I've just pushed it on
<https://github.com/dvarrazzo/psycopg>.

Cheers,

-- Daniele

psycopg by date:

Previous
From: Karsten Hilbert
Date:
Subject: Re: getquoted and unicode
Next
From: "Carl S. Yestrau Jr."
Date:
Subject: Re: getquoted and unicode