From: | KaiGai Kohei <kaigai(at)kaigai(dot)gr(dot)jp> |
---|---|
To: | Itagaki Takahiro <itagaki(dot)takahiro(at)oss(dot)ntt(dot)co(dot)jp> |
Cc: | Albe Laurenz <laurenz(dot)albe(at)wien(dot)gv(dot)at>, pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: TRIGGER with WHEN clause |
Date: | 2009-11-16 11:03:24 |
Message-ID: | 4B01317C.3050308@kaigai.gr.jp |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers pgsql-rrreviewers |
Albe Laurenz wrote:
> SQL> CREATE TRIGGER dummy BEFORE DELETE ON employees WHEN (1 = 1)
> 2 BEGIN
> 3 END;
> 4 /
> CREATE TRIGGER dummy BEFORE DELETE ON employees WHEN (1 = 1)
> *
> ERROR at line 1:
> ORA-04077: WHEN clause cannot be used with table level triggers
Thanks for your information.
> I am also not sure about Oracle, but I think there are usage of
> statement trigger with WHEN cluase something like:
> =# CREATE TRIGGER log_trig BEFORE UPDATE ON tbl
> WHEN (is_superuser()) EXECUTE PROCEDURE log_current_stmt();
Itagaki-san, I also think your example usage is enough valueable.
However, Oracle does not have the feature apparently, although the
purpose of this patch is to provide a compatible feature, IIRC.
I don't have any preference on either of them.
If you make a decision, I'll review the patch according to your
decision. So, I like to ask you which is your preference again.
Thanks,
--
KaiGai Kohei <kaigai(at)kaigai(dot)gr(dot)jp>
From | Date | Subject | |
---|---|---|---|
Next Message | Boszormenyi Zoltan | 2009-11-16 11:05:22 | ECPG patch 4, out-of-scope cursor support in Informix-mode |
Previous Message | Boszormenyi Zoltan | 2009-11-16 11:00:44 | Re: ECPG patch 3, DESCRIBE [OUTPUT] support |
From | Date | Subject | |
---|---|---|---|
Next Message | Alex Hunsaker | 2009-11-16 17:31:47 | Re: CommitFest 2009-11: Initial assignments |
Previous Message | Albe Laurenz | 2009-11-16 10:42:37 | Re: TRIGGER with WHEN clause |