Skip site navigation (1)
Skip section navigation (2)
Peripheral Links
Header And Logo
|
Site Navigation
Re: Return the primary key of a newly inserted row?
- From: Alban Hertroys <alban(at)magproductions(dot)nl>
- To: John Tregea <john(at)debraneys(dot)com>
- Cc: Scott Ribe <scott_ribe(at)killerbytes(dot)com>, Kenneth Downs <ken(at)secdat(dot)com>, Tim Allen <tim(at)proximity(dot)com(dot)au>, pgsql-general(at)postgresql(dot)org
- Subject: Re: Return the primary key of a newly inserted row?
- Date: Mon, 26 Jun 2006 11:31:32 +0200
John Tregea wrote:
The example of select id1 = nextval(somesequence)could work for me. I have multiple users with our GUI and imagine I could use transaction protection to ensure no duplicates between selecting and incrementing the somesequence...
You won't have duplicates[1], it's a sequence. It's its purpose. Now I may have missed something, I didn't follow this thread.[1] Unless you manage to make it wrap around after 2^32 (or 2^64?) calls of nextval. But that's quite unlikely.
-- Alban Hertroys alban(at)magproductions(dot)nl magproductions b.v. T: ++31(0)534346874 F: ++31(0)534346876 M: I: www.magproductions.nl A: Postbus 416 7500 AK Enschede // Integrate Your World //
- Follow-Ups:
- Re: Return the primary key of a newly inserted row?
- From: Scott Ribe
- Re: Return the primary key of a newly inserted row?
- From: Martijn van Oosterhout
- Re: Return the primary key of a newly inserted row?
- References:
- Re: Return the primary key of a newly inserted row?
- From: Scott Ribe
- Re: Return the primary key of a newly inserted row?
- From: John Tregea
- Re: Return the primary key of a newly inserted row?
- Prev by Date: inheritance and table
- Next by Date: Re: update impossible, constraint prevents it but it shouldn't
- Previous by thread: Re: Return the primary key of a newly inserted row?
- Next by thread: Re: Return the primary key of a newly inserted row?
- Indexes: