Date: Tue, 30 Jun 2015 00:17:47 -0700 (MST)
From: gmb <gmbouwer@gmail.com>
To: pgsql-sql@postgresql.org
Message-ID: <1435648667132-5855844.post@n5.nabble.com>
In-Reply-To: <55915587.2020606@aklaver.com>
References: <1435563798887-5855658.post@n5.nabble.com>
 <559142D5.2080608@aklaver.com> <1435587185136-5855697.post@n5.nabble.com>
 <55915587.2020606@aklaver.com>
Subject: Re: Disable Trigger for session only
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Precedence: bulk
Sender: pgsql-sql-owner@postgresql.org

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.


-- 
Sent via pgsql-sql mailing list (pgsql-sql@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-sql