pg.ddx.io  pgsql-sql@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Ross J. Reedstrom <reedstrm@rice.edu>
To: pgsql-sql@postgresql.org
Subject: Re: INSERT question
Date: Thu, 15 Nov 2001 16:03:38 -0600
Message-ID: <20011115160338.D4187@rice.edu> (raw)
In-Reply-To: <m21yizhkej.fsf@tycho.rlent.pnet>
References: <1f5f2b44.0111130130.17e8e57a@posting.google.com>
	<3bf19679$0$189$e4fe514c@newszilla.xs4all.nl>
	<878zd7vpzn.fsf@npa01zz001.simplot.com>
	<m21yizhkej.fsf@tycho.rlent.pnet>

On Thu, Nov 15, 2001 at 03:03:00PM -0500, Roland Roberts wrote:
> >>>>> "Jason" == Jason Earl <jason.earl@simplot.com> writes:
> 
>     Jason> Even better, however, is to use the functions nextval() and
>     Jason> currval() like so:
> 
>     Jason> INSERT INTO parent_table (data) values ('some data');
>     Jason> INSERT INTO child_table (parent, more_data) 
>     Jason>         (currval('parent_table_p_key_seq'), 
>     Jason>          'more data');
> 
> The above is probably the best for a pure-SQL way with the caveat
> that it should be wrapped in a transaction or currval() may not be
> what you expect; i.e., another client may add a row and you get a
> value different from what you inserted.

This is one of the only FMAQ I've ever seen: (Frequently Mis-Answered
Question)

Read the docs for currval(): it returns the value _last sent to
this connection_, so is multiuser safe. The _only_ caveat is that in
the presence of connection pooling, your problem as described might
occur. However, since the two inserts above _should_ be wrapped in a
transaction, I'd say any connection pool that shares a connection with
an open transaction on it is broken, anyway.

Ross



view thread (12+ messages)  latest in thread

Message-ID: <20011115160338.D4187@rice.edu>
Permalink:  ../20011115160338.D4187@rice.edu/
Also on:    postgresql.org/message-id/20011115160338.D4187@rice.edu

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: pgsql-sql@postgresql.org
  Cc: reedstrm@rice.edu
  Subject: Re: INSERT question
  In-Reply-To: <20011115160338.D4187@rice.edu>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox