Oracle FAQ | Your Portal to the Oracle Knowledge Grid |
Home -> Community -> Usenet -> c.d.o.server -> Re: serializable isolation level behavior question
joeNOSPAM_at_BEA.com wrote:
>>>> I would question the reason for would allowing two different isolation >>>> levels within a single application. What is the business case? >>>> -- >>>> Daniel A. Morgan >>> Hi Dan. I didn't notice where anyone was limiting to one application >>> or specifying multiple isolation levels. Let us posit one application >>> that hopes to use Oracle's serializable isolation level, and one >>> rogue/bumbling admin that mistakenly truncates a table. Should >>> Oracle behave as claimed for the application's serializable tx? >>> JoeBumbling or not ... if that admin truncates a production table while >> people are using the app I would expect that to be their last day of >> employment. >> >> You are correct no one limited it to a single app. But if it was two >> different apps I would expect that they would never be hitting the >> same objects. >> -- >> Daniel A. Morgan >> University of Washington
Bob Jones is pointing out, correctly, that TRUNCATE is DDL: Not DML.
Given that he is correct about this then I would expect that the behaviour given a truncate should be the same as that from DROP TABLE. With that consideration how do you feel about what you are observing?
-- Daniel A. Morgan University of Washington damorgan_at_x.washington.edu (replace x with u to respond) Puget Sound Oracle Users Group www.psoug.orgReceived on Thu Oct 19 2006 - 11:20:26 CDT