From: | Jitendra Loyal <jitendra(dot)loyal(at)gmail(dot)com> |
---|---|
To: | pgsql-general(at)lists(dot)postgresql(dot)org |
Subject: | Use case for BEFORE STATEMENT level trigger |
Date: | 2019-03-14 05:38:23 |
Message-ID: | CAGBkuseoBcOyobwU66+1fBcRcJ7-e=9BvfqT8uh0HucETAHtRA@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
I had been wondering as to where one can use BEFORE STATEMENT level
trigger, more so because one does not know (access) what rows are getting
affected. Only thing which comes to my mind is that if one wants to do
something at a table-level, then this trigger can be used; this is quite
unusual though as I have not experienced this need in more than two decades
of developing business applications. I am looking forward to some one who
can enlighten me with the use case because I may be missing something.
Thanks
From | Date | Subject | |
---|---|---|---|
Next Message | Noah Misch | 2019-03-14 05:42:54 | Re: LDAP authenticated session terminated by signal 11: Segmentation fault, PostgresSQL server terminates other active server processes |
Previous Message | Thomas Munro | 2019-03-14 04:18:49 | Re: LDAP authenticated session terminated by signal 11: Segmentation fault, PostgresSQL server terminates other active server processes |