Re: register_hstore does DB queries, does not play well with async connections - Mailing list psycopg

From Daniele Varrazzo
Subject Re: register_hstore does DB queries, does not play well with async connections
Date
Msg-id AANLkTikEL5RM7f_+WiVvChz0KY2MXwhxeptQPyFAhiBg@mail.gmail.com
Whole thread Raw
In response to Re: register_hstore does DB queries, does not play well with async connections  (Jan Urbański <wulczer@wulczer.org>)
List psycopg
On Mon, Feb 21, 2011 at 9:32 AM, Jan Urbański <wulczer@wulczer.org> wrote:
> On 21/02/11 10:24, Daniele Varrazzo wrote:
>> On Sun, Feb 20, 2011 at 10:08 PM, Jan Urbański <wulczer@wulczer.org> wrote:

>>> BTW: the query assumes you have hstore installed in the "public" schema,
>>> which might not be correct... How about allowing passing the
>>> fully-qualified type name to register_hstore?
>>
>> Is this really a real use case? the 'public' schema is specified in
>> contrib/hstore.sql so you would need to hack the installer to put the
>> hstore somewhere else.
>
...
> But you're right, you can always use the oid kwarg in that case. I think
> we could just document that the adapter assumes public.hstore and if you
> have it elswhere you should use the oid kwarg.

The issue has been raised in ticket #45 too. And I realized that is no
problem at all to register the typecaster for all the hstore OIDs
found in the different schemas. So no additional parameter to specify
the schema: the register_hstore in 2.4 will just work (tm).

-- Daniele

psycopg by date:

Previous
From: mani sabri
Date:
Subject: _psycopg.vc9.x86.manifest
Next
From: Jason Erickson
Date:
Subject: Re: _psycopg.vc9.x86.manifest