| From: | gmb <gmbouwer(at)gmail(dot)com> |
|---|---|
| To: | pgsql-sql(at)postgresql(dot)org |
| Subject: | Re: Disable Trigger for session only |
| Date: | 2015-06-30 07:17:47 |
| Message-ID: | 1435648667132-5855844.post@n5.nabble.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-sql |
Adrian Klaver-4 wrote
> That I do not know. A thought did come to mind though. That is to add a
> reset boolean column(default ='f') to your detail table and make the
> trigger procedure aware of it. Then when you are resetting the values to
> zero have reset = 't' and have the trigger procedure ignore those rows.
> Then do the 'normal' update to update the summary table.
Thanks Adrian, this will be a workable solution and I'll take it into
account.
One problem is that many will view the addition of another column for this
purpose to be unjustified.
--
View this message in context: http://postgresql.nabble.com/Disable-Trigger-for-session-only-tp5855658p5855844.html
Sent from the PostgreSQL - sql mailing list archive at Nabble.com.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | gmb | 2015-06-30 08:31:37 | Re: Disable Trigger for session only |
| Previous Message | Adrian Klaver | 2015-06-29 20:43:35 | Re: Disable Trigger for session only |