Re: Record Lock under Commitment Control -- MIDRANGE-L

Subject: Re: Record Lock under Commitment Control
From: Patrik Schindler <poc@xxxxxxxxxx>
Date: Wed, 23 Feb 2022 16:50:07 +0100
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>

Hello Rob,

Am 23.02.2022 um 16:30 schrieb Rob Berendt <rob@xxxxxxxxx>:

A "deadly embrace" was when USERA locked a record like this, let's say CUSTA. Then USERB locks a record like this, lets say CUSTB. Now if USERA tries to read CUSTB without updating CUSTA (F12 perhaps) it doesn't release the record of CUSTA and waits on CUSTB. If USERB does the same thing by switching to CUSTA then they are both waiting perpetually for the other to unlock their rows.

Thanks for pointing that out. Because I use explicit UNLOCKs in any case (even with F12 being pressed), this (in theory) can't happen.

:wq! PoC

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.