Oracle FAQ Your Portal to the Oracle Knowledge Grid
HOME | ASK QUESTION | ADD INFO | SEARCH | E-MAIL US
 

Home -> Community -> Usenet -> c.d.o.misc -> Re: Unlocking

Re: Unlocking

From: Thomas Kyte <tkyte_at_us.oracle.com>
Date: Fri, 04 Feb 2000 11:19:45 -0500
Message-ID: <kuul9ssp81s9jv80icdrjh8r5kf3rltp24@4ax.com>


A copy of this was sent to Mike Cox <Mike.Cox_at_orchard-systems.co.uk> (if that email address didn't require changing) On Fri, 4 Feb 2000 10:29:35 -0000 , you wrote:

>Maxime,
>
>If you "update" the record(s) locked by the "select for update" it
>removes the locks
>

no it doesn't. commiting or rolling back is the only way to remove the locks.

>-----Original Message-----
>From: Maxime Tardif [mailto:maxime.tardif_at_cgi.ca]
>Posted At: 03 February 2000 16:13
>Posted To: misc
>Conversation: Unlocking
>Subject: Unlocking
>
>
>I use the "select for update" and I must do a commit or a rollback for
>unlocking the record. Our problem is that we use only one connection
>and we
>do more than one transaction but we want to post only one of them. I
>can't
>use a transaction because the select for update is already in the
>transaction and I don't want to post this transaction. Do you know an
>other
>manner for managing the lock?
>

--
See http://osi.oracle.com/~tkyte/ for my columns 'Digging-in to Oracle8i'... Current article is "Part I of V, Autonomous Transactions" updated June 21'st  

Thomas Kyte                   tkyte_at_us.oracle.com
Oracle Service Industries     Reston, VA   USA

Opinions are mine and do not necessarily reflect those of Oracle Corporation Received on Fri Feb 04 2000 - 10:19:45 CST

Original text of this message

HOME | ASK QUESTION | ADD INFO | SEARCH | E-MAIL US