RE: Monitoring for Database Updates. -- MIDRANGE-L

× 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.

We did this before journaling.  Problem?  DFU and other non-program access
to the file.

Buck Calabro
Billing Concepts Albany, NY
mailto:mcalabro@commsoft.net

> -----Original Message-----
> From: Pat Barber 
> Sent: Wednesday, July 28, 1999 5:09 PM
> To:   MIDRANGE-L@midrange.com
> Subject:      Re: Monitoring for Database Updates.
> 
> Colin Williams wrote:
> > 
> > Is there any way to monitor for changes to a file, without using
> > journalling or triggers.
> 
> Prior to "trigger" days, I always wrote a small "logging" program
> that would kick in anytime the update occurred....Took a "snap shot"
> of entire record coming in, and then compared record at update time...
> I would write out the "before" & "after" record to my log file...
> 
+---
| This is the Midrange System Mailing List!
| To submit a new message, send your mail to MIDRANGE-L@midrange.com.
| To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com.
| To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com
+---

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