"Ross J. Reedstrom" wrote:
> Gah, this is getting a bit annoying, correcting this bit of
> mis-information.
>
> currval() is kept as part of the session context, as is completely
> multi-user safe. That's why the person you quoted said 'in the same
> session'.
>
> Where is everyone coming up with
Gah, this is getting a bit annoying, correcting this bit of
mis-information.
currval() is kept as part of the session context, as is completely
multi-user safe. That's why the person you quoted said 'in the same
session'.
Where is everyone coming up with the wrong idea on this? Is there a
major
---
The reboots are for hardware upgrades!
"http://www.nmmm.nu; <[EMAIL PROTECTED]>
- Original Message -
From: Adriaan Joubert <[EMAIL PROTECTED]>
Cc: Dev Elop <[EMAIL PROTECTED]>; pgsql-general
<[EMAIL PROTECTED]>
Sent: 09 Äåêåìâðè 1
> > With this second method, you'd probably need to beware race conditions. If
> > another process inserts a record into mytable after you do but before you
> > call currval(), then you'll get the wrong value.
> >
> > Not an issue if you've only got one process accessing the table - probably
> > i
On Thu, 9 Dec 1999, Dev Elop wrote:
> > >
> > > After an INSERT, I want to retrieve the value of the sequence I use for
> > > unique_ids
> > >
> ...
> >
> > Alternatively, use the currval(mytable_id_seq) function within the same
> > session immediately after the insert.
> >
> With this second met
> >
> > After an INSERT, I want to retrieve the value of the sequence I use for
> > unique_ids
> >
...
>
> Alternatively, use the currval(mytable_id_seq) function within the same
> session immediately after the insert.
>
With this second method, you'd probably need to beware race conditions. If
an
Kevin Heflin wrote:
> I've been looking through the online docs, so far have not found this
> information.
>
> After an INSERT, I want to retrieve the value of the sequence I use for
> unique_ids
>
> Any suggestions ?
Use the OID returned from the INSERT to select the newly created value,
i.e.,
