Re: Changing isolation level?

mcstock wrote:
> "Daniel Morgan" <damorgan_at_x.washington.edu> wrote in message
> news:1070486233.549645_at_yasure...
> | D Alpern wrote:
> |
> | > SELECT... FOR UPDATE {WAIT | NOWAIT} springs to mind...
> | >
> | > David
> |
> | Why would that spring to mind?
> |
> | It doesn't block a read which is the point of the OP's request.
> |
> | --
> | Daniel Morgan
> | http://www.outreach.washington.edu/ext/certificates/oad/oad_crs.asp
> | http://www.outreach.washington.edu/ext/certificates/aoa/aoa_crs.asp
> | damorgan_at_x.washington.edu
> | (replace 'x' with a 'u' to reply)
> |
>
> actually, it does... it voluntarily blocks the read that it itself
> (grammar?) is attempting to do
>
> so, on a case by case basis (instead of a session or instance isolation
> level setting), the reader gets blocked by the writer
>
> unfortunately, the reader that uses this syntax now blocks writers, but if
> serialization is what's required to meet the business requirement, this
> would seem to do it

You are correct as you stated it but not as the OP did. The OP wanted to   grab a record for update and stop anyone else from viewing the updated record while, or until, the person that grabbed it for update performed a commit.

It isn't going to happen in Oracle.

You can select for update and stop me from updating or deleting. But you can't stop me from reading the record.

-- 
Daniel Morgan
http://www.outreach.washington.edu/ext/certificates/oad/oad_crs.asp
http://www.outreach.washington.edu/ext/certificates/aoa/aoa_crs.asp
damorgan_at_x.washington.edu
(replace 'x' with a 'u' to reply)