Bruno Wolff III wrote:
> On Fri, Jan 06, 2006 at 19:11:27 +0200,
>   Marko Kreen <[EMAIL PROTECTED]> wrote:
> > On 1/6/06, Bruce Momjian <> wrote:
> > 
> > Considering there's no currval() without nextval(), what point
> > is disallowing currval() when user is able to call nextval()?
> > 
> > I rather want to allow nextval/currval and disable setval as it
> > allows regular user to DoS the database.
> What I was thinking with this, is that you might allow someone the ability
> to insert records into a table which would make use of nextval, but not
> allow them to run nextval directly. But after inserting a record allow them
> to use currval to see what value was assigned.
> People could still mess with things by doing INSERTs and aborting the
> transaction, so this may not be the best example for why you would want this.

That seems too confusing to support based on usefulness of the new

  Bruce Momjian                        |               |  (610) 359-1001
  +  If your life is a hard drive,     |  13 Roberts Road
  +  Christ can be your backup.        |  Newtown Square, Pennsylvania 19073

---------------------------(end of broadcast)---------------------------
TIP 2: Don't 'kill -9' the postmaster

Reply via email to