Skip site navigation (1) Skip section navigation (2)

Re: nextval() clarification

From: Michael Fuhr <mike(at)fuhr(dot)org>
To: Greg Donald <destiney(at)gmail(dot)com>
Cc: pgsql-novice(at)postgresql(dot)org
Subject: Re: nextval() clarification
Date: 2004-09-13 22:02:26
Message-ID: 20040913220226.GA55308@winnie.fuhr.org (view raw or flat)
Thread:
Lists: pgsql-novice
On Mon, Sep 13, 2004 at 03:55:41PM -0500, Greg Donald wrote:
> On Mon, 13 Sep 2004 21:54:11 +0200, Ennio-Sr <nasr(dot)laili(at)tin(dot)it> wrote:
> > I think you should put <nextval(....)> directly into the INSERT
> > instruction, so that it advances only once per added record.
> > Have a look at Documentation PostgreSQL 7.4, Ch 9.11, table 9.34.
> > HTH
> 
> I would but then I don't know how to ensure I return that exact same
> id from the insert, like mysql_insert_id() does.  That's the whole
> reason why I aquire the id first, so I know what it is after the
> insert.  SELECT max(id) would be off under load I think.

Are you aware of CURRVAL()?

CREATE TABLE foo (
    id    SERIAL PRIMARY KEY,
    info  TEXT NOT NULL
);

INSERT INTO foo (info) VALUES ('First Item');
INSERT INTO foo (info) VALUES ('Second Item');
SELECT CURRVAL('foo_id_seq');

-- 
Michael Fuhr
http://www.fuhr.org/~mfuhr/

In response to

pgsql-novice by date

Next:From: Mitch PirtleDate: 2004-09-14 00:41:00
Subject: Re: Opinions Requested - PG API or Abstraction Layer
Previous:From: Ron St-PierreDate: 2004-09-13 22:01:10
Subject: Re: nextval() clarification

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group