Re: Avoiding redundant triggers? -- MIDRANGE-L

× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.

Subject: Re: Avoiding redundant triggers?
From: "James H. H. Lampert" <jamesl@xxxxxxxxxxxxxxxxx>
Date: Tue, 01 Feb 2011 09:08:20 -0800
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>

Dennis wrote:

Not sure what you mean about the One Trigger Per Slot rule - since
there has never been such a restriction in DB2/400.

Actually, several revisions back (before named triggers; as recently as V4R4), there was exactly such a restriction: ONE "before" and ONE "after" trigger each, for "insert," "update," and "delete," for a total of six triggers per file, one per slot.

--
JHHL

As an Amazon Associate we earn from qualifying purchases.

Follow-Ups:

Re: Avoiding redundant triggers? , Dennis

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.