RE: Triggers -- MIDRANGE-L

Subject: RE: Triggers
From: Ian Scotson <IanS@xxxxxxxxxxxx>
Date: Fri, 7 Dec 2001 13:39:54 +1100
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/cgi-bin/listinfo/midrange-l>,<mailto:midrange-l-request@midrange.com?subject=subscribe>
List-Unsubscribe: <http://lists.midrange.com/cgi-bin/listinfo/midrange-l>,<mailto:midrange-l-request@midrange.com?subject=unsubscribe>

Alex,

When you say "other Process" - are you talking of via a Dataq
or somenting like that?

Ian.
-----Original Message-----
From: Alex A Moore [mailto:alexm@ellishosiery.com]
Sent: Friday, 7 December 2001 12:33
To: midrange-l@midrange.com
Subject: RE: Triggers

We use triggers extensively.  If you follow a few simple guidelines, there
is no noticeable performance "hit".  The most basic and important rule is -
ONLY PERFORM ESSENTIAL LOGIC WITHIN THE TRIGGER PROGRAM.  When possible,
perform NO logic - just pass the buffers on to a separate process.  If the
trigger program calls other programs, or opens and closes a bunch of
database files, or performs the unpardonable sin of causing another trigger
to fire, you will NOT be happy.

Alex  ( Don't ask how I know )

As an Amazon Associate we earn from qualifying purchases.

Follow-Ups:

RE: Triggers , Alex A Moore

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.