Re: table locks in cursor. how it works?
Posted by:
Rick James
Date: October 01, 2012 07:42PM
The one notable mistake is having the FOR UPDATE outside the START...COMMIT transaction.
I don't see the need for a VIEW -- why not just construct the SELECT, then execute it?
With those two changes, you might not need the "locks" you asked about.
Subject
Views
Written By
Posted
6081
September 24, 2012 02:37AM
2367
September 28, 2012 01:35PM
2205
September 30, 2012 01:53PM
Re: table locks in cursor. how it works?
1687
October 01, 2012 07:42PM
1505
October 02, 2012 12:45AM
1475
October 02, 2012 08:33AM
1504
October 03, 2012 03:46PM
1323
October 03, 2012 11:26PM
1565
October 04, 2012 12:12AM
1336
October 04, 2012 08:28AM
Sorry, you can't reply to this topic. It has been closed.
Content reproduced on this site is the property of the respective copyright holders.
It is not reviewed in advance by Oracle and does not necessarily represent the opinion
of Oracle or any other party.