Have the trigger send a message to a data queue and have a data queue
monitor watch for messages. Have it send the e-mails. Put as little logic as
possible in the trigger.

The before and after images are just that. Images of the record before and
after the change. For a insert operation you only have a after image, for a
delete operation only a before image and for a update both.

Consider using my trigger mediator at www.think400.dk/downloads.htm. At
least read the read me on problems with triggers.

On Mon, May 9, 2011 at 8:56 PM, jmmckee <jmmckee@xxxxxxxxxxxxxx> wrote:

We are looking into a process to notify doctors, via email, when one of
their patients has been admitted. When a patient is admitted, a record is
written to a log file. Current idea being tossed around is to read the log
file from the previous day and srnd emails as needed. I thought this might
be an ideal application for a trigger program. I could see the trigger
getting fired on a write to the log file. All I would want to do is pass
the data to be written to a program and the program would either send or not
send an email. From looking at some documentation, I see that there is
space for a before and an after image.

These sound like dumb questions to me: Is it as simple as referencing the
log file as an external data structure? Then, moving the after image to
that data structure?

John McKee

This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.

As an Amazon Associate we earn from qualifying purchases.

This thread ...


Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

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