From: | Andrew Dunstan <andrew(at)dunslane(dot)net> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | Martijn van Oosterhout <kleptog(at)svana(dot)org>, Thomas Hallgren <thomas(at)tada(dot)se>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: User Defined Types in Java |
Date: | 2006-02-09 14:41:33 |
Message-ID: | 43EB549D.2010708@dunslane.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Tom Lane wrote:
>Martijn van Oosterhout <kleptog(at)svana(dot)org> writes:
>
>
>>Actually, I'm think this whole automatic creation of a shell-type a bit
>>silly anyway. Why not simply solve the problem directly like so:
>>
>>
>
>
>
>>CREATE TYPE complex AS SHELL;
>>
>>
>
>One of the unwritten consequences of the way that it works now is that
>only superusers can "clutter the catalogs" with shell types.
>
>
I suppose we could restrict this variant to superusers, at least initially.
[snip]
>Having said that, I agree that this seems conceptually cleaner, though
>I'm not sure we could ever get rid of the old way because of backward
>compatibility issues.
>
>
>
They are not mutually exclusive, are they? I too like Martijn's suggestion.
cheers
andrew
From | Date | Subject | |
---|---|---|---|
Next Message | Marko Kreen | 2006-02-09 14:44:20 | Re: streamlined standby procedure |
Previous Message | Andrew Dunstan | 2006-02-09 14:38:00 | Re: pg_hba.conf alternative |