| From: | Florian Pflug <fgp(at)phlo(dot)org> |
|---|---|
| To: | James William Pye <lists(at)jwp(dot)name> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Robert Haas <robertmhaas(at)gmail(dot)com>, Jan Urbański <wulczer(at)wulczer(dot)org>, Postgres - Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: hstores in pl/python |
| Date: | 2010-12-15 14:57:27 |
| Message-ID: | 28163BEC-6BC8-4ACB-8745-554E8CDC0525@phlo.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Dec15, 2010, at 02:14 , James William Pye wrote:
> On Dec 13, 2010, at 6:16 PM, Tom Lane wrote:
>> how do you identify which type OID is really hstore?
>
> How about an identification field on pg_type?
>
> CREATE TYPE hstore ..., IDENTIFIER 'org.postgresql.hstore';
> -- Where the "identifier" is an arbitrary string.
+1
I've wanted something like this a few times when dealing
with custom types within a client. A future protocol version
might even transmit these identifiers instead a the type's OID,
thereby removing the dependency on OID from clients entirely.
best regards,
Florian Pflug
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Dimitri Fontaine | 2010-12-15 15:00:31 | Re: hstores in pl/python |
| Previous Message | Tom Lane | 2010-12-15 14:57:18 | Re: Default mode for shutdown |