RE: Lock
Date: Mon, 12 Mar 2012 07:08:15 -0500
Message-ID: <C5533BD628A9524496D63801704AE56D6ADD5C136B_at_SPOBMEXC14.adprod.directory>
From a technical perspective, no not really.
You would want to know the Oracle behavior - could you imagine if Oracle created one lock for EACH row affected by an update/insert/delete statement in a very active OLTP (type) system? DBAs would have to then be managing lock parameters by expected transactions and users I would think.
Chris Taylor
"Quality is never an accident; it is always the result of intelligent effort."
-- John Ruskin (English Writer 1819-1900)
Any views and/or opinions expressed herein are my own and do not necessarily reflect the views of Ingram Industries, its affiliates, its subsidiaries or its employees.
-----Original Message-----
From: oracle-l-bounce_at_freelists.org [mailto:oracle-l-bounce_at_freelists.org] On Behalf Of Mercadante, Thomas F (LABOR)
Sent: Monday, March 12, 2012 7:02 AM
To: andy_at_oracledepot.com; toon.koppelaars_at_rulegen.com
Cc: cure_at_austin.rr.com; oracle-l_at_freelists.org
Subject: RE: Lock
Isn't this a mute point?
No other session can see these records until they are committed. So even if they are locked, what's the difference?
--
http://www.freelists.org/webpage/oracle-l
--
http://www.freelists.org/webpage/oracle-l
Received on Mon Mar 12 2012 - 07:08:15 CDT