RE: Locking of record using SQL in JAVA Websphere application. -- JAVA400-L

Subject: RE: Locking of record using SQL in JAVA Websphere application.
From: "D*B" <dieter.bender@xxxxxxxxxxxx>
Date: Wed, 10 Oct 2012 17:24:25 +0200
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 IBM i <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>

<Dan>
Under commitment control, I don't think "FOR UPDATE" is going to preclude another thread from reading the same record. You have to rely on deleteRow() to throw an exception in the thread that loses the race.
</Dan>

... depends on isolation READ_COMMITTED, REPEATABLE_READ and SERIALIZABLE should put a sufficient lock to the record till end of transaction

As an Amazon Associate we earn from qualifying purchases.

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.