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 [EMAIL PROTECTED]
and data management solutions (415) 565-7293
for law firms, small businesses fax 621-2533
and non-profit organizations. San Francisco
---------------------------(end of broadcast)---------------------------
TIP 1: subscribe and unsubscribe commands go to [EMAIL PROTECTED]
