Re: nextval/dbi question - Mailing list pgsql-novice

From harrold@sage.che.pitt.edu
Subject Re: nextval/dbi question
Date
Msg-id Pine.LNX.4.21.0108051905050.18298-100000@sage.che.pitt.edu
Whole thread Raw
In response to Re: nextval/dbi question  (Horst Herb <hherb@malleenet.net.au>)
List pgsql-novice
john
There is no operating system but linux and linus is its kernel maintainer.

Sometime in August Horst Herb assaulted keyboard and produced...

|On Monday 06 August 2001 08:47, harrold@sage.che.pitt.edu wrote:
|
|> i was under the impression that nextval would give what the nextval would
|> be. i didnt think it was suppose to increment it. after reading your
|> response and someone else's it seems i need to get the next value of the
|> key and insert it explicitly is that correct?
|
|Yes. Alternatively, you can let Postgres use nextval implicitly, and call
|currval afterwards to get the value of the inserted "nextval"
|

thanks.
one more question. what can i do to prevent another insert from taking
place before the currval request is made? is this even an issue aslong as
the currval query is executed using the same connection?

john



pgsql-novice by date:

Previous
From: Tom Lane
Date:
Subject: Re: nextval/dbi question
Next
From: harrold@sage.che.pitt.edu
Date:
Subject: Re: nextval/dbi question