Received: from gnumed.dhs.org (modem59.malleenet.net.au [203.143.67.123] (may be forged)) by postgresql.org (8.11.3/8.11.4) with SMTP id f7U3ddf15358 for ; Wed, 29 Aug 2001 23:39:40 -0400 (EDT) (envelope-from hherb@malleenet.net.au) Received: (qmail 2674 invoked by uid 8); 30 Aug 2001 03:39:28 -0000 Received: from pc-00071.e-smith.gnumed.dhs.org (192.168.1.71, claiming to be "munin.gnumed.dhs.org") by bifrost.e-smith.gnumed.dhs.org with SMTP id smtpdsviueV; Thu, 30 Aug 2001 13:39:19 EST Content-Type: text/plain; charset="iso-8859-1" From: Horst Herb To: "omid omoomi" , PostgreSQL-development Subject: Re: Re: [SQL] getting the oid for a new tuple in a BEFORE trigger Date: Thu, 30 Aug 2001 13:40:49 +1000 X-Mailer: KMail [version 1.2] References: In-Reply-To: MIME-Version: 1.0 Message-Id: <01083013404901.26591@munin.gnumed.dhs.org> Content-Transfer-Encoding: 8bit X-Archive-Number: 200108/994 X-Sequence-Number: 12798 On Wednesday 29 August 2001 20:05, you wrote: > hi, > Idon't know the best way but how about a quick insert in a temp table and > adding 1 to the inserted oid column each time the trigger will run.! > regards As you don't know how many users access the server concurrently and in which order they will be served you will probably noty get what you want unless you work on a single user single client-server connection all the time. Horst