Re: nextval() clarification

From: Greg Donald <destiney(at)gmail(dot)com>
To: pgsql-novice(at)postgresql(dot)org
Subject: Re: nextval() clarification
Date: 2004-09-13 20:55:41
Message-ID: ea9da26c040913135570c29353@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-novice

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.

I just didn't understand why it appeared to be +2 and not +1 as a
novice might expect. But now I get it. Thanks to all.

--
Greg Donald
http://destiney.com/

In response to

Responses

Browse pgsql-novice by date

  From Date Subject
Next Message vhikida 2004-09-13 21:29:10 Re: Subnovice question
Previous Message Ron St-Pierre 2004-09-13 20:41:15 Re: nextval() clarification