From: | Alban Hertroys <alban(at)magproductions(dot)nl> |
---|---|
To: | Bob Pawley <rjpawley(at)shaw(dot)ca> |
Cc: | Postgresql <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: After Trigger |
Date: | 2006-09-22 08:52:17 |
Message-ID: | 4513A441.80401@magproductions.nl |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Bob Pawley wrote:
>
> I am seeking wording for a procedure that will initiate a trigger only
> after another trigger has completed its function. In this case I want to
> drop a table that is created and used by the first trigger.
You could just call a function from your trigger, or handle it inside
the trigger.
An alternative approach would be to use a permanent table, fill it
within your transaction and trunk it eventually. To other transactions
there'll never be any data in it, and you lose the overhead of creating
and dropping the table (replacing it by trunking...).
--
Alban Hertroys
alban(at)magproductions(dot)nl
magproductions b.v.
T: ++31(0)534346874
F: ++31(0)534346876
M:
I: www.magproductions.nl
A: Postbus 416
7500 AK Enschede
// Integrate Your World //
From | Date | Subject | |
---|---|---|---|
Next Message | Ragnar | 2006-09-22 09:01:54 | Re: Can i switch to the use of persistent connections |
Previous Message | Matthias.Pitzl | 2006-09-22 07:53:00 | Re: Strange database corruption with PostgreSQL 7.4.x o |