I have to agree with that. I didnt really want to get into that
discussion. But, I believe not reading uncommitted data is part
of the defining specification for a relational database.
Lets not get into the discussion of whether or not Oracle is a truly
relational database or not.
On 7/12/07, Bobak, Mark <Mark.Bobak@il.proquest.com> wrote:
IMHO, the fact that Oracle doesn't support uncommitted read isolation level is a feature, not a bug!
-Mark
--
Mark J. Bobak
Senior Database Administrator, System & Product Technologies
ProQuest
789 E. Eisenhower, Parkway, P.O. Box 1346
Ann Arbor MI 48106-1346
734.997.4059 or 800.521.0600 x 4059
mark.bobak@il.proquest.com
www.proquest.com
www.csa.com
ProQuest...Start here.
-----Original Message-----
From: oracle-l-bounce@freelists.org
[mailto:oracle-l-bounce@freelists.org] On Behalf Of Buchanan, Jason
Sent: Thursday, July 12, 2007 3:03 PM
To: hkchital@singnet.com.sg
Cc: niall.litchfield@gmail.com; DBA Deepak; oracle-l
Subject: Re: ISOLATION LEVEL
On Jul 10, 2007, at 10:48 AM, Hemant K Chitale wrote:
> An Oracle query never reads dirty (uncommitted) data.
Uncommitted Read isolation level is one of the few nice features of
DB2 that is lacking in Oracle.
--
http://www.freelists.org/webpage/oracle-l
--
http://www.freelists.org/webpage/oracle-l
--
Andrew W. Kerber
'If at first you dont succeed, dont take up skydiving.'