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


  • Subject: Re: Commit or Journal?
  • From: DAsmussen@xxxxxxx
  • Date: Fri, 19 Sep 1997 01:12:41 -0400 (EDT)

Dave,

In a message dated 97-09-19 00:26:49 EDT, you write:

> How do you test whether the record has changed? Method 1 - store the
>  entire record and then compare the current value of each field that your
>  update would change with its stored value. Method 2 - have an update
>  time stamp on the record and simply compare that with it's previous
>  value.

Or, move the initial read into a data structure.  Move the second read into
another data structure of equal length, and compare the two.  The timestamp
can be inadequate unless you're using the new "extended length" time -- my
old employer had (packaged) programs start blowing up when the "D" models
came out because some of them based unique keys on the old "TIME" keyword.
 Seems the "D" facilitated processing multiple records within the same
second.  Method 3?

Regards,

Dean Asmussen
Enterprise Systems Consulting, Inc.
Fuquay-Varina, NC  USA
E-Mail:  DAsmussen@AOL.COM

"BPCS -- Better Programs Coming Soon."
+---
| This is the Midrange System Mailing List!
| To submit a new message, send your mail to "MIDRANGE-L@midrange.com".
| To unsubscribe from this list send email to MAJORDOMO@midrange.com
|    and specify 'unsubscribe MIDRANGE-L' in the body of your message.
| Questions should be directed to the list owner/operator: david@midrange.com
+---


As an Amazon Associate we earn from qualifying purchases.

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