Expanding from "rules" (i.e., what's PERMITTED) into "conventions"
(i.e., what's SENSIBLE):
Especially if there is a reason to enable and disable triggers
programmatically (but also in general), I would also recommend that if
explicitly applying a name (instead of just taking what the system gives
you), it should be concise but distinctive, avoids collisions, and
clearly identifies the trigger's purpose.
For example, if the trigger is part of XYZ application, invoking
XYZTRGF123 on updates to file F123, "Fred" would be a bad choice
(concise, but irrelevant);
"TheUpdateTriggerToInvokeXYZTRGF123_on_update_of_F123" would also be a
bad choice (ridiculously verbose), but "XYZTRGF123_UPD" would be a good
choice, assuming that F123 is the only file for which XYZTRGF123 is a
trigger program.
--
JHHL
As an Amazon Associate we earn from qualifying purchases.
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.
midrange.com
