Re: Preventing recursive call exceptions on triggers, or at least keeping them out of the joblog? -- MIDRANGE-L

Subject: Re: Preventing recursive call exceptions on triggers, or at least keeping them out of the joblog?
From: rob@xxxxxxxxx
Date: Thu, 16 May 2013 13:23:56 -0400
List-archive: <http://archive.midrange.com/midrange-l>
List-help: <mailto:midrange-l-request@midrange.com?subject=help>
List-id: Midrange Systems Technical Discussion <midrange-l.midrange.com>
List-post: <mailto:midrange-l@midrange.com>
List-subscribe: <http://lists.midrange.com/mailman/listinfo/midrange-l>, <mailto:midrange-l-request@midrange.com?subject=subscribe>
List-unsubscribe: <http://lists.midrange.com/mailman/listinfo/midrange-l>, <mailto:midrange-l-request@midrange.com?subject=unsubscribe>

Let me ask this, if some action updates FILEA, and there's a trigger on
FILEA it does not attempt to update that same row in FILEA by either an
SQL update or an rla update, does it? Because it's better to do that by
ALWRPTCHG(*YES) and modifying the trigger buffer.
Or is it more of a case where row A gets triggered and that trigger
updates row B and the trigger on row B attempts to update row A again?

Rob Berendt

As an Amazon Associate we earn from qualifying purchases.

Follow-Ups:

Re: Preventing recursive call exceptions on triggers, or at least keeping them out of the joblog? , James H. H. Lampert

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.