From: Josh Berkus <josh@agliodbs.com>
To: Markus Wagner <wagner@imsd.uni-mainz.de>
To: pgsql-sql@postgresql.org
Subject: Re: getting the oid for a new tuple in a BEFORE trigger
Date: Wed, 29 Aug 2001 07:38:00 -0700
Message-ID: <web-110336@davinci.ethosmedia.com> (raw)
In-Reply-To: <01082911150802.01558@jumbo>
Mark,
The responses to your problem are gonna be kinda slow, as 2/3 of the
core team, and many of the users, are at the Expo right now (and if
anyone on the list is in the SF Bay Area, join us! BOF session
tonight!)
> 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.
What problem?
> 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.
Once again, why?
> Is there any way (even hack) to get the oid the newly inserted tuple
> will
> receive?
This specific answer will have to come from someone else.
I could suggest a couple of workarounds, if you gave a fuller
description of exactly what you're trying to accomplish.
-Josh Berkus
P.S. Please do not cross-post to more than 2 lists at a time. The
Postgres lists have been kept to a managable volume to date; let's keep
it that way.
______AGLIO DATABASE SOLUTIONS___________________________
Josh Berkus
Complete information technology josh@agliodbs.com
and data management solutions (415) 565-7293
for law firms, small businesses fax 621-2533
and non-profit organizations. San Francisco
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-sql@postgresql.org
Cc: josh@agliodbs.com, wagner@imsd.uni-mainz.de
Subject: Re: getting the oid for a new tuple in a BEFORE trigger
In-Reply-To: <web-110336@davinci.ethosmedia.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox