Pro*C and Locking Mechanism
From: Dogan Cibiceli <dcib_at_gwl.com>
Date: Thu, 18 Mar 1999 16:00:36 -0700
Message-ID: <36F18594.DD2AEC25_at_gwl.com>
Hi,
[Quoted] The question might be obvious to most but nevertheless I would like to know the answer. My question is about release and obtaining locks. When a Pro*C program starts to execute and acquires locks as it goes, does it hold all locks it acquired until it comes across a commit ? Let'say I have selected (NO Update OF Clause) some values from a bunch of tables and updated a bunch of tables, and inserted and deleted some stuff. I go on in this manner. This module will hold all the locks it acquired from the start until I issue a commit. Is that right ? Thanks in advance :)
Date: Thu, 18 Mar 1999 16:00:36 -0700
Message-ID: <36F18594.DD2AEC25_at_gwl.com>
Hi,
[Quoted] The question might be obvious to most but nevertheless I would like to know the answer. My question is about release and obtaining locks. When a Pro*C program starts to execute and acquires locks as it goes, does it hold all locks it acquired until it comes across a commit ? Let'say I have selected (NO Update OF Clause) some values from a bunch of tables and updated a bunch of tables, and inserted and deleted some stuff. I go on in this manner. This module will hold all the locks it acquired from the start until I issue a commit. Is that right ? Thanks in advance :)
Dogan Received on Fri Mar 19 1999 - 00:00:36 CET