Re: Avoiding redundant triggers? -- MIDRANGE-L

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

Charles Wilt wrote:

Very simple rule...NAME YOUR TRIGGERS!

Don't let the system generate a name for your trigger.

If the triggers have a name, then the system will ensure that only one
of that trigger is attached to the file.

. . .

AHA! I knew there HAD to be something simple, that I was missing!

Thanks! Danke! Gracias! Grazie! Merci! tlho'!

On what level is trigger-name uniqueness enforced? File? Library? System-wide?

--
JHHL

Follow-Ups:

Re: Avoiding redundant triggers? , Charles Wilt
Re: Avoiding redundant triggers? , Luis Rodriguez

This mailing list archive is Copyright 1997-2026 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.