× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



I think this is an intelligent and cogent explanation of both the power and
perils of triggers, David.  As I look at what you're saying, triggers and
I/O modules together can do some very nice things.  It's when people use
triggers as an excuse to allow ad hoc updates to the database that I get a
bit perturbed.

What would be nice is a way to set a flag in a job that says "bypass
triggers"; if I had that level of granularity in my requests, I'd be very
happy.

Since my client/server models always use I/O modules (it's the nature of the
design), I haven't had to use triggers a great deal.  I'll keep this
discussion in mind in future design session, though.

Thanks!

Joe


> -----Original Message-----
> From: David Morris
>
> A trigger does not preclude security checking in an I/O module
> and can actually
> enhance it.  I have used a combination of triggers and I/O
> modules (in fact they
> are the same program) for a few years.



As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:
Replies:

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

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.