Re: Changing isolation level?

| 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)
|

if the environment allows critical write transactions in a poorly controlled manner, yes

i know the feature-issue is getting write to block reads, but the presumption seems to be that the reads are being done in the context of a pending write transaction. with proper security and design, including a TAPI for all DML, the functionality could be designed in for transactions where it matters.

there should be no issue with non-updating transactions -- just use SET TRANSACTION READ ONLY for multi-statement read consistency.

• mcs