| From: | Shane Ambler <pgsql(at)007Marketing(dot)com> |
|---|---|
| To: | Bob Pawley <rjpawley(at)shaw(dot)ca>, PostgreSQL Mailing lists <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: After Trigger |
| Date: | 2006-09-22 05:24:50 |
| Message-ID: | C139A9BA.4EA66%pgsql@007Marketing.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On 22/9/2006 2:14, "Bob Pawley" <rjpawley(at)shaw(dot)ca> 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.
Sounds like you should use a temporary table.
CREATE TEMP TABLE mytmptable (......
This table will just disappear shortly after your trigger is finished.
--
Shane Ambler
Postgres(at)007Marketing(dot)com
Get Sheeky @ http://Sheeky.Biz
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bo Lorentsen | 2006-09-22 05:47:10 | Re: Replication and PITR |
| Previous Message | Charles Ambrose | 2006-09-22 04:19:52 | Re: Backup Large Tables |