RE: Serializable isolation level behavior question

From: Allen, Brandon <Brandon.Allen_at_OneNeck.com>
Date: Mon, 16 Oct 2006 13:52:21 -0700
Message-ID: <04DDF147ED3A0D42B48A48A18D574C45059E217C@NT15.oneneck.corp>

I'm guessing that a TRUNCATE TABLE is a special situation, and that a DROP TABLE would probably have the same effect since they are both DDL - maybe the serializable isolation doesn't apply to them like it does to DML statements such as DELETE. Did you test with a DELETE instead of TRUNCATE? That should definitely give you the expected result.  

---

        From: oracle-l-bounce_at_freelists.org
[mailto:oracle-l-bounce_at_freelists.org] On Behalf Of Harvinder Singh

	Sent: Monday, October 16, 2006 1:36 PM
	To: oracle-l
	Subject: Serializable isolation level behavior question
	
	

	Hi,

	 

	We are testing concurrency performance and trying to isolate the

issue using sqlplus and some dummy tables and need some clarification.          

Privileged/Confidential Information may be contained in this message or attachments hereto. Please advise immediately if you or your employer do not consent to Internet email for messages of this kind. Opinions, conclusions and other information in this message that do not relate to the official business of this company shall be understood as neither given nor endorsed by it.

--
http://www.freelists.org/webpage/oracle-l

Received on Mon Oct 16 2006 - 15:52:21 CDT