Re: nextval() clarification - Mailing list pgsql-novice

From Ron St-Pierre
Subject Re: nextval() clarification
Date
Msg-id 414618A6.7040806@syscor.com
Whole thread Raw
In response to Re: nextval() clarification  (Greg Donald <destiney@gmail.com>)
List pgsql-novice
Greg Donald wrote:

>On Mon, 13 Sep 2004 21:54:11 +0200, Ennio-Sr <nasr.laili@tin.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.
>
>
>
After your insert statement, you can call CURRVAL to find out what the
value was that you
inserted into the serial column.

eg SELECT currval('companies_company_id_seq'::text)

Ron


pgsql-novice by date:

Previous
From:
Date:
Subject: Re: Subnovice question
Next
From: Michael Fuhr
Date:
Subject: Re: nextval() clarification