Re: [SQL] getting the oid for a new tuple in a BEFORE trigger - Mailing list pgsql-general

From omid omoomi
Subject Re: [SQL] getting the oid for a new tuple in a BEFORE trigger
Date
Msg-id F180zhad2VqKwRPQIWD0000059a@hotmail.com
Whole thread Raw
List pgsql-general
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
Omid
>From: Markus Wagner <wagner@imsd.uni-mainz.de>
>To: pgsql-general@postgresql.org, pgsql-sql@postgresql.org,
>pgsql-hackers@postgresql.org
>Subject: [SQL] getting the oid for a new tuple in a BEFORE trigger
>Date: Wed, 29 Aug 2001 11:15:08 +0200
>
>Hi,
>
>we need to control database changes within BEFORE triggers.
>There is no problem with triggers called by update, but there is
>a problem with triggers called by insert.
>
>We strongly need to know the oid of a newly inserted tuple. In this case,
>we
>use tg_newtuple of the TriggerData structure passed to thetrigger function,
>and its t_data -> t_oid will have the value '0'.
>
>Using BEFORE and AFTER triggers would make our lives much harder.
>
>Is there any way (even hack) to get the oid the newly inserted tuple will
>receive?
>
>Thank you very much,
>
>Markus
>
>
>---------------------------(end of broadcast)---------------------------
>TIP 3: if posting/reading through Usenet, please send an appropriate
>subscribe-nomail command to majordomo@postgresql.org so that your
>message can get through to the mailing list cleanly


_________________________________________________________________
Get your FREE download of MSN Explorer at http://explorer.msn.com/intl.asp


pgsql-general by date:

Previous
From: Shanmugasundaram
Date:
Subject: Regarding vacuumdb
Next
From: Justin Clift
Date:
Subject: Re: RFC: PostgreSQL and MySQL comparison.