Of couse you could offload the processing to a separate program using a data queue to avoid the performance hit - I've done that - it's more work up front, but actually quite simple.

I've not noticed any major 'hit' with triggers, especially if you preload stuff into arrays, as I suggested. Of course, that's assuming you're not printing or calling a web service or something equally performance intensive..........

--- Original Message ---
From:vhamberg@xxxxxxxxxxx

Triggers are synchronous - are run inline with the database process - so they can delay things.

Journals are, too, of course, but you can run your compare afterwards - asynchronously - and have no effect on the database activity.

Eh?

Vern


This thread ...

Follow-Ups:

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

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