| From: | Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com> |
|---|---|
| To: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> |
| Cc: | stan <stanb(at)panix(dot)com>, pgsql-general <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: Detecting which columns a query will modify in a function called by a trigger |
| Date: | 2020-03-03 23:11:35 |
| Message-ID: | 19a1796f-8fe0-d2ee-e8a5-809d5eba787c@aklaver.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-docs pgsql-general |
On 3/3/20 3:06 PM, David G. Johnston wrote:
> On Tue, Mar 3, 2020 at 3:48 PM Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com
> <mailto:adrian(dot)klaver(at)aklaver(dot)com>> wrote:
>
> The link was for automatically updateable views. If you want to do
> something more involved then see:
>
> https://www.postgresql.org/docs/12/rules-views.html#RULES-VIEWS-UPDATE
>
>
> CREATE TRIGGER works with views; I usually see recommendations to start
> there and avoid rules if at all possible.
The above suggests triggers then rules.
>
> David J.
--
Adrian Klaver
adrian(dot)klaver(at)aklaver(dot)com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | David G. Johnston | 2020-03-03 23:19:08 | Re: Detecting which columns a query will modify in a function called by a trigger |
| Previous Message | David G. Johnston | 2020-03-03 23:06:44 | Re: Detecting which columns a query will modify in a function called by a trigger |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | David G. Johnston | 2020-03-03 23:19:08 | Re: Detecting which columns a query will modify in a function called by a trigger |
| Previous Message | David G. Johnston | 2020-03-03 23:06:44 | Re: Detecting which columns a query will modify in a function called by a trigger |