From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | ohp(at)pyrenet(dot)fr |
Cc: | pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: Bug or feature? |
Date: | 2001-05-12 16:48:19 |
Message-ID: | 9858.989686099@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Olivier PRENANT <ohp(at)pyrenet(dot)fr> writes:
> Shoudn't postgres extend priviledges to the sequences generated by a
> create table ???
That's not clear. The sequence is an independent object. Had you
explicitly done
CREATE SEQUENCE myseq;
CREATE TABLE mytab (f1 int default nextval('myseq'));
would you expect that granting permissions on mytab automatically
grants them on myseq as well? I think you might consider that
surprising. But there isn't any difference between this and what
CREATE TABLE does.
There have been suggestions in the past that SERIAL should be a "real
data type" with the sequence object being hidden more effectively than
it is now --- including auto-dropping it at table deletion, etc.
If that were to happen then the permissions issue would probably go away
too. It doesn't seem to be a very high priority for anyone, though.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Olivier PRENANT | 2001-05-12 17:17:03 | Re: Bug or feature? |
Previous Message | Olivier PRENANT | 2001-05-12 16:36:59 | Re: Bug or feature? |