Received: from localhost (postgresql.org [64.49.215.8]) by postgresql.org (Postfix) with ESMTP id 0E906475E5D for ; Wed, 28 Aug 2002 12:36:07 -0400 (EDT) Received: from web12907.mail.yahoo.com (web12907.mail.yahoo.com [216.136.174.74]) by postgresql.org (Postfix) with SMTP id 3D6D4475DD7 for ; Wed, 28 Aug 2002 12:36:06 -0400 (EDT) Message-ID: <20020828163610.70353.qmail@web12907.mail.yahoo.com> Received: from [80.19.150.245] by web12907.mail.yahoo.com via HTTP; Wed, 28 Aug 2002 18:36:10 CEST Date: Wed, 28 Aug 2002 18:36:10 +0200 (CEST) From: =?iso-8859-1?q?friedrich=20nietzsche?= Subject: Re: [SQL] Retrieving the new "nextval" for primary keys.... To: pgsql-sql Cc: pgsql-general@postgresql.org, pgsql-sql@postgresql.org In-Reply-To: <3D6CF5B7.90206@nurseamerica.net> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Virus-Scanned: by AMaViS new-20020517 X-Archive-Number: 200209/82 X-Sequence-Number: 29663 One solution seems to locking table(s), but I prefer to leave it as last chance... using table locks, and the trick of writing and suddenly reading back from DB it probably works, but it doesn't seems so sexy... :) ciao danilo ______________________________________________________________________ Yahoo! Musica: notizie, recensioni, classifiche, speciali multimediali http://it.yahoo.com/mail_it/foot/?http://it.music.yahoo.com/