Re: Record Lock under Commitment Control -- 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.

Subject: Re: Record Lock under Commitment Control
From: Charles Wilt <charles.wilt@xxxxxxxxx>
Date: Wed, 23 Feb 2022 07:07:45 -0700
List-archive: <https://archive.midrange.com/midrange-l/>
List-post: <mailto:midrange-l@lists.midrange.com>
List-subscribe: <https://lists.midrange.com/mailman/listinfo/midrange-l>, <mailto:midrange-l-request@lists.midrange.com?subject=subscribe>
List-unsubscribe: <https://lists.midrange.com/mailman/options/midrange-l>, <mailto:midrange-l-request@lists.midrange.com?subject=unsubscribe>

On Wed, Feb 23, 2022 at 5:57 AM Patrik Schindler <poc@xxxxxxxxxx> wrote:

In addition, I have found that after acquiring a lock on a record with
some flavor of READ, or CHAIN, after being done with that record (UPDATE),
I must add an explicit UNLOCK into my code, or the record stays locked. I
observed this behavior *without* commitment control. I don't know if this
behavior changes then commitment control is in effect. I'm still at the
beginning with experimenting.

Ah no, you don't have to UNLOCK after an UPDATE...

Something else is going on.

Charles

As an Amazon Associate we earn from qualifying purchases.

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.