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 15:01:03 |
Message-ID: | CALL-XePeFfzP6HMJUSmrcHW5gm+OBAnZGuhCAK+=WL+a_xb4OQ@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Yes a rule can rewrite query or replace the query
Read through Depesz post about rules and the weird side affects that can
occurr
https://www.depesz.com/2010/06/15/to-rule-or-not-to-rule-that-is-the-question/
On Sat, Mar 7, 2020 at 9:57 AM stan <stanb(at)panix(dot)com> wrote:
> On Sat, Mar 07, 2020 at 09:47:39AM -0500, Justin wrote:
> > 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
> >
>
> So, the RULE can actually rewrite the query, instead of replacing it,
> which is what I m doing in the function, correct?
> --
> "They that would give up essential liberty for temporary safety deserve
> neither liberty nor safety."
> -- Benjamin Franklin
>
From | Date | Subject | |
---|---|---|---|
Next Message | Ashkar Dev | 2020-03-07 19:29:51 | duplicate key value violates unique constraint |
Previous Message | stan | 2020-03-07 14:57:18 | Re: Rules versus triggers |