From: Aasmund Midttun Godal <postgresql@envisity.com>
To: pgsql-sql@postgresql.org
Subject: Sequence permission suggestion
Date: Mon, 26 Nov 2001 00:55:14 GMT
Message-ID: <20011126005514.10436.qmail@ns.krot.org> (raw)
Today it seems that the following rules governs the permissions of sequences:
SELECT - allow you to select * from seq_name;
INSERT - no effect
UPDATE - allows nextval, setval - and yes implicitly currval
DELETE - no effect
I suggest nextval is moved into the insert permission as this is quite natural - normally you only need to call nextval when you insert a new value into a table. I think this issue is important because setting the sequence to a value lower than the max value in a table will cause errors for other users.
Aasmund Midttun Godal
aasmund@godal.com - http://www.godal.com/
+47 40 45 20 46
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-sql@postgresql.org
Cc: postgresql@envisity.com
Subject: Re: Sequence permission suggestion
In-Reply-To: <20011126005514.10436.qmail@ns.krot.org>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox