From: | Justin <zzzzz(dot)graf(at)gmail(dot)com> |
---|---|
To: | stan <stanb(at)panix(dot)com> |
Cc: | "pgsql-generallists(dot)postgresql(dot)org" <pgsql-general(at)lists(dot)postgresql(dot)org> |
Subject: | Re: Rules versus triggers |
Date: | 2020-03-07 14:47:39 |
Message-ID: | CALL-XeORpZyTBLSjn-vw5Xhs_cKdv-P-WB420xbWiGwC57MA3A@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Hi Stan
Rules actual are able to rewrite the SQL query sent to postgresql. Most
everyone suggestion is avoid rules.
Triggers are just like every other databases Triggers firing off code for
Insert/Update/Delete/Truncate event
https://www.postgresql.org/docs/current/sql-createtrigger.html
On Sat, Mar 7, 2020 at 6:56 AM stan <stanb(at)panix(dot)com> wrote:
> Could someone give me a brief description of the intended functionally, and
> how the 2 features work of rules, versus triggers? It appears to me that
> they are simply 2 different ways to set up triggers, but I am certain that
> is just because of my lack of knowledge.
>
> Thank you.
>
> --
> "They that would give up essential liberty for temporary safety deserve
> neither liberty nor safety."
> -- Benjamin Franklin
>
>
>
From | Date | Subject | |
---|---|---|---|
Next Message | Andy Colson | 2020-03-07 14:51:35 | Re: geting results of query in plperl |
Previous Message | Steve Atkins | 2020-03-07 14:38:09 | Re: Rules versus triggers |