| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Dmitry Tkach <dmitry(at)openratings(dot)com> |
| Cc: | pgsql-bugs(at)postgresql(dot)org, pgsql-general(at)postgresql(dot)org |
| Subject: | Re: [GENERAL] INSTEAD rule bug? |
| Date: | 2003-07-15 16:53:34 |
| Message-ID: | 23479.1058288014@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs pgsql-general |
Dmitry Tkach <dmitry(at)openratings(dot)com> writes:
> I know... That was a typo in my sql :-)
> But for this example it doesn't matter - that view/table is only needed
> to illustrate the rules behaviour on insert.
Oh, I see what you're on about. Sorry, a "DO INSTEAD NOTHING" only
suppresses the original command, it does not suppress other rules.
I think what you want is to make the insert_test rule conditional
on x being not null.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Dmitry Tkach | 2003-07-15 17:00:47 | Re: [GENERAL] INSTEAD rule bug? |
| Previous Message | Tom Lane | 2003-07-15 16:45:25 | Re: Another bug with views |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bruno Wolff III | 2003-07-15 16:53:50 | Re: perfromance impact of vacuum |
| Previous Message | Dmitry Tkach | 2003-07-15 16:45:01 | Re: INSTEAD rule bug? |