From: | Daniele Varrazzo <daniele(dot)varrazzo(at)gmail(dot)com> |
---|---|
To: | Jan Urbański <wulczer(at)wulczer(dot)org> |
Cc: | Psycopg List <psycopg(at)postgresql(dot)org> |
Subject: | Re: register_hstore does DB queries, does not play well with async connections |
Date: | 2011-02-25 00:45:16 |
Message-ID: | AANLkTikEL5RM7f_+WiVvChz0KY2MXwhxeptQPyFAhiBg@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | psycopg |
On Mon, Feb 21, 2011 at 9:32 AM, Jan Urbański <wulczer(at)wulczer(dot)org> wrote:
> On 21/02/11 10:24, Daniele Varrazzo wrote:
>> On Sun, Feb 20, 2011 at 10:08 PM, Jan Urbański <wulczer(at)wulczer(dot)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
From | Date | Subject | |
---|---|---|---|
Next Message | Jason Erickson | 2011-02-25 01:03:13 | Re: _psycopg.vc9.x86.manifest |
Previous Message | mani sabri | 2011-02-24 19:10:49 | _psycopg.vc9.x86.manifest |