From: | Joe Conway <mail(at)joeconway(dot)com> |
---|---|
To: | Rod Taylor <rbt(at)zort(dot)ca> |
Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Remove implicit unique index creation on SERIAL columns? |
Date: | 2002-08-18 19:02:43 |
Message-ID: | 3D5FEF53.9010005@joeconway.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Rod Taylor wrote:
>>>In MSSQL this
>>>is gotten around by allowing the properties of the data type to be
>>>altered, e.g. in MSSQL you can turn the IDENTITY property on or off
>>
>>Rather pointless if it can be turned off, wouldn't you say?
>>
>>What I would do if I wanted such a guarantee is to make insertions
>>go through a view rule that prevents the serial column from being
>
>
> In the future if we have per column privileges, we could disable insert
> and update on serial columns by default for everyone but the table owner
> and super-users (to accommodate dataloads).
That sounds like the best way-to-go.
> Till then a trigger or view will do the job for those who wish to add
> them.
Agreed.
Joe
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2002-08-18 19:31:12 | Re: [PATCHES] Better handling of parse errors |
Previous Message | Tom Lane | 2002-08-18 17:19:17 | Re: Open 7.3 issues |