Re: read uncommited

From: Frank Swarbrick <Frank.Swarbrick_at_efirstbank.com>
Date: Fri, 27 Nov 2009 10:02:48 -0700
Message-ID: <4B0FA3C8.6F0F.0085.0_at_efirstbank.com>



>>> On 11/25/2009 at 12:42 PM, in message <4b0d96bf$1_at_news.victoria.tc.ca>, Malcolm Dew-Jones<yf110_at_vtn1.victoria.tc.ca> wrote:
> Frank Swarbrick (Frank.Swarbrick_at_efirstbank.com) wrote:
> : In DB2 you can do something like the following:
>
> : SELECT *
> : FROM MYTABLE
> : WITH UR;
>
> : If you have, say, a batch application that is inserting a lot of rows
> in to
> : a table, with no commits until the end of the job, doing the above
> query
> : while the batch update job is still running will allow you to see the
> : inserted but not yet committed rows.
>
> : Not something that you would want to do with a user application, but
> it's
> : something that as a developer I have found occasionally useful (seeing
> what
> : my batch job is "doing" before it's actually done).
>
> : Is there any such feature available for Oracle?
>
> No, Oracle prevents you from seeing data until it's committed.

I did google a bit and thought that Oracle would not allow it, but wanted to verify by actually asking the question myself. I guess I can understand why the decision was made. Not sure I agree with the reasoning, but... Probably not a big deal in the end. Thanks!

Frank

-- 

Frank Swarbrick
Applications Architect - Mainframe Applications Development
FirstBank Data Corporation - Lakewood, CO  USA
P: 303-235-1403
Received on Fri Nov 27 2009 - 11:02:48 CST

Original text of this message