| From: | Christoph Dalitz <christoph(dot)dalitz(at)hs-niederrhein(dot)de> |
|---|---|
| To: | Jean-Luc Lachance <jllachan(at)nsd(dot)ca> |
| Cc: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>, Tino Wildenhain <tino(at)wildenhain(dot)de>, pgsql-general(at)postgresql(dot)org |
| Subject: | Re: ALTER TRIGGER DISABLE/ENABLE |
| Date: | 2002-11-28 08:33:57 |
| Message-ID: | 20021128093357.48c9d644.christoph.dalitz@hs-niederrhein.de |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Tue, 26 Nov 2002 14:41:47 -0500
Jean-Luc Lachance <jllachan(at)nsd(dot)ca> wrote:
>
> I think thte sintax should be:
>
> ALTER TABLE DISABLE|ENABLE TRIGGER {trigger name}|ALL
>
This would make no sense:
It could be the syntax if the statement for creating a trigger
where "ALTER TABLE ADD TRIGGER".
The statement for creating a trigger is however "CREATE TRIGEER".
Consequently the statement for changing a trigger must be "ALTER TRIGGER"
and not "ALTER TABLE".
Switching off all triggers for an individual table at once would be
convenient of course and can be easily achieved with "ALTER TRIGGER" as well:
just write a little PL/SQL procedure "disable_triggers()" that takes a
tablename as input and disables all triggers on it.
Christoph Dalitz
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Madhavi | 2002-11-28 09:31:27 | Createlang PLTCLU failed |
| Previous Message | Tom Lane | 2002-11-28 07:08:39 | Re: Two features left |