Markus Wagner writes:
> 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
On Wed, Aug 29, 2001 at 11:15:08AM +0200, Markus Wagner wrote:
> 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 inse
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 pro
ject: [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 inse
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 pa
