Re: Locking records in DB2 -- JAVA400-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.

Subject: Re: Locking records in DB2
From: "Paul Morgan" <pmorgan@xxxxxxxxxxxxxx>
Date: Wed, 5 Oct 2005 14:29:50 -0400
List-archive: <http://archive.midrange.com/java400-l>
List-help: <mailto:java400-l-request@midrange.com?subject=help>
List-id: Java Programming on and around the iSeries / AS400 <java400-l.midrange.com>
List-post: <mailto:java400-l@midrange.com>
List-subscribe: <http://lists.midrange.com/mailman/listinfo/java400-l>, <mailto:java400-l-request@midrange.com?subject=subscribe>
List-unsubscribe: <http://lists.midrange.com/mailman/listinfo/java400-l>, <mailto:java400-l-request@midrange.com?subject=unsubscribe>

Joe,

You're assuming the entire record gets updated but that might not be the
case.  For example I might have a customer file with billing and ship to
addresses on one customer record.  Just because the billing address got
updated while the ship to address was being edited doesn't mean we have to
throw away the ship to update.  Having one counter for the entire record
wouldn't allow concurrent updates to different parts of the record.

Paul

As an Amazon Associate we earn from qualifying purchases.

Follow-Ups:

RE: Locking records in DB2 , Joe Pluta

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.