From: | "Tambet Matiisen" <t(dot)matiisen(at)aprote(dot)ee> |
---|---|
To: | "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | <pgsql-sql(at)postgresql(dot)org> |
Subject: | Re: calling function from rule |
Date: | 2003-01-23 15:55:39 |
Message-ID: | 81132473206F3A46A72BD6116E1A06AE1B14CC@black.aprote.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-sql |
>
> "Tambet Matiisen" <t(dot)matiisen(at)aprote(dot)ee> writes:
> > I have a view and update rule on it, which updates another
> table. Now I would like to call a function, after update of
> the table is done. Also the function must be called in the
> same transaction as update. I tried to define an additional
> update rule on the view, but doing a SELECT in update rule
> spoils the affected records count:
>
> Try 7.3, we changed the rules about returned records count.
> http://www.ca.postgresql.org/users-lounge/docs/7.3/postgres/ru
> les-status.html
>
I have 7.3. When rule and action are the same, everything works fine.
Doing an insert in update rule and opposite are OK too. Problem is,
when I do select in insert/update/delete rule. Then the result of
select is returned instead of command status, even if the select
is done in non-instead rule and there is unconditional instead rule.
See the example in my previous mail.
Tambet
From | Date | Subject | |
---|---|---|---|
Next Message | Stephan Szabo | 2003-01-23 16:53:53 | Re: To use a VIEW or not to use a View..... |
Previous Message | Tom Lane | 2003-01-23 15:30:00 | Re: calling function from rule |