From: | Martijn van Oosterhout <kleptog(at)svana(dot)org> |
---|---|
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:12:30 |
Message-ID: | 20051110171230.GF19686@svana.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Thu, Nov 10, 2005 at 12:02:58PM -0500, Andrew Dunstan wrote:
>
> 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.
Why? What's wrong with creating the functions when people use the
module, like every other module in contrib? Is there a reason you need
fixed oids?
Have a nice day,
--
Martijn van Oosterhout <kleptog(at)svana(dot)org> http://svana.org/kleptog/
> Patent. n. Genius is 5% inspiration and 95% perspiration. A patent is a
> tool for doing 5% of the work and then sitting around waiting for someone
> else to do the other 95% so you can sue them.
From | Date | Subject | |
---|---|---|---|
Next Message | Andrew Dunstan | 2005-11-10 17:17:54 | Re: generic builtin functions |
Previous Message | Andrew Dunstan | 2005-11-10 17:02:58 | generic builtin functions |