[prev in list] [next in list] [prev in thread] [next in thread] 

List:       postgresql-general
Subject:    Re: [GENERAL] trigger is holding up the data
From:       "Gregory Wood" <gregw () com-stock ! com>
Date:       2001-12-31 16:14:45
[Download RAW message or body]

Why not make the trigger that performs the insert into event an AFTER
trigger? Assuming that you don't need to modify the values, that should
allow you to read any values that were just inserted/updated. If not, you
should be able to split the triggers into both BEFORE and AFTER to achieve
the results you want.

Greg

----- Original Message -----
From: "Nate Haggard" <nate@wordplace.com>
To: <pgsql-general@postgresql.org>
Sent: Friday, December 28, 2001 6:13 PM
Subject: [GENERAL] trigger is holding up the data


> I have a database with multiple tables.  I have a trigger set on the event
> table.  When events occur a tuple is inserted into event and the trigger
is
> activated.  In the trigger program I also want to look up data in other
> tables based on the data inserted into the event table.  Usually the data
I
> want to see from the other tables does not exist until the trigger program
> has exited.  How can I make the trigger activate only after all tables in
> the database have been changed.  It would still trigger on new events, but
> it wouldn't run the program till all the tables that needed to be updated
> were updated.
>
> Thanks
> Nate
>
>
> ---------------------------(end of broadcast)---------------------------
> TIP 5: Have you checked our extensive FAQ?
>
> http://www.postgresql.org/users-lounge/docs/faq.html
>


---------------------------(end of broadcast)---------------------------
TIP 1: subscribe and unsubscribe commands go to majordomo@postgresql.org
[prev in list] [next in list] [prev in thread] [next in thread]