×
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.
On Tue, Jan 13, 2009 at 9:45 AM, Booth Martin <booth@xxxxxxxxxxxx> wrote:
chain (n) That will provide non-locking. If you are read-only, its not
a problem. It just works.
If you aren't read only, you have to worry about updates.
http://en.wikipedia.org/wiki/Optimistic_locking
Basically, save a before image. When time to update, compare
the before image (or a time stamp, if the record has one) the
the record to be updated. If they aren't the same, *don't do it*
(send the user telling them to reinquire and reupdate due to
underlying database change).
I use this when my I/O in encapsulated into a batch program, serving
multiple (interactive) clients. Works well.
Chris
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
