From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Andrew Dunstan <andrew(at)dunslane(dot)net> |
Cc: | PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: generic builtin functions |
Date: | 2005-11-10 17:48:57 |
Message-ID: | 10375.1131644937@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Andrew Dunstan <andrew(at)dunslane(dot)net> writes:
> I am looking at creating a few generic functions builtin for the enum
> stuff. These would be tied to each enum type as it is created. However,
> they should not really appear in pg_proc initially, as there wouldn't be
> any enum types to tie them to anyway. But I want them to have reserved
> oids and appear in the list of builtins.
This feels wrong to me. Ways that might work include:
1. Invent a pseudotype 'anyenum' comparable to 'anyarray', and define
the generic functions as taking 'anyenum'.
2. Don't try to define the generic operations as true functions, but
make them special syntactic constructs comparable to ROW() or ARRAY[].
I think I like #1 better, but it's hard to be sure when discussing
it in a vacuum. How about being more specific about what you want
to accomplish?
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Kevin Grittner | 2005-11-10 18:00:12 | Re: Comments from a Firebird user via Borland |
Previous Message | Rod Taylor | 2005-11-10 17:46:41 | Re: Possible savepoint bug |