| From: | Andrew Dunstan <andrew(at)dunslane(dot)net> |
|---|---|
| To: | Martijn van Oosterhout <kleptog(at)svana(dot)org> |
| Cc: | PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: generic builtin functions |
| Date: | 2005-11-10 17:17:54 |
| Message-ID: | 437380C2.5000203@dunslane.net |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Martijn van Oosterhout wrote:
>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?
>
>
>
>
This is not intended for contrib. The whole point of the exercise is to
have language support, which means either it's builtin or it doesn't
happen. See my email with a general outline from a few days ago.
cheers
andrew
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Rod Taylor | 2005-11-10 17:46:41 | Re: Possible savepoint bug |
| Previous Message | Martijn van Oosterhout | 2005-11-10 17:12:30 | Re: generic builtin functions |