Received: from ns.krot.org (ns.krot.org [193.212.103.165]) by postgresql.org (8.11.3/8.11.4) with SMTP id fAQ0uIm25834 for ; Sun, 25 Nov 2001 19:56:19 -0500 (EST) (envelope-from postgresql@envisity.com) Received: (qmail 2571 invoked by uid 67); 26 Nov 2001 00:55:14 -0000 Message-ID: <20011126005514.10436.qmail@ns.krot.org> Content-Type: text/plain; charset=ISO-8859-1 Content-Disposition: inline MIME-Version: 1.0 From: "Aasmund Midttun Godal" To: pgsql-sql@postgresql.org Subject: Sequence permission suggestion Date: Mon, 26 Nov 2001 00:55:14 GMT X-Mailer: Googley-Moogley Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by postgresql.org id fAQ13En26102 X-Archive-Number: 200111/359 X-Sequence-Number: 5741 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