×
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 agree. However, it won't help the OP with the performance hit caused by
read triggers.
Seems rather odd to me that database I/O is cached by default. But you have
to license that feature for journals.
Regarding the performance hit on read triggers, I think Jim hit the nail on
the head by suggesting an asynchronous process and using a data queue. We
use a similar process. Except we use shared memory between the trigger
program and an external JOB which we call a database event handler to pass
record buffers, which is even faster than a data queue.
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
