| From: | Daniele Varrazzo <daniele(dot)varrazzo(at)gmail(dot)com> |
|---|---|
| To: | Tobias Oberstein <tobias(dot)oberstein(at)gmail(dot)com> |
| Cc: | Ronan Dunklau <rdunklau(at)gmail(dot)com>, psycopg(at)postgresql(dot)org |
| Subject: | Re: flexi adaption/casting scheme |
| Date: | 2012-09-22 13:30:22 |
| Message-ID: | CA+mi_8YQcsqYpMY7YP1k06uDquuaRysPWt=dq-wpBHcMXsWu7g@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | psycopg |
On Sat, Sep 22, 2012 at 2:25 PM, Tobias Oberstein
<tobias(dot)oberstein(at)gmail(dot)com> wrote:
> the _from_db class method on CompositeCaster takes a name argument and
> parsed that into "schema" and "typename".
>
> It uses both to retrieve Oids etc, but then only forwards "typename", and
> not "schema" to the CompositeCaster constructor.
>
> If a have 2 composite types defined "public.t_foo" and "bar.t_foo", and
> register both, one will be overwritten ..
Uhm... why overwritten? The two CompositeCaster will register two
different typecasters on two different oids. The name is only used as
name namedtuple name. What would the schema be used for?
-- Daniele
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tobias Oberstein | 2012-09-22 13:44:02 | Re: flexi adaption/casting scheme |
| Previous Message | Tobias Oberstein | 2012-09-22 13:25:17 | Re: flexi adaption/casting scheme |