Path: dp-news.maxwell.syr.edu!spool.maxwell.syr.edu!news-spur1.maxwell.syr.edu!news.maxwell.syr.edu!newshub.sdsu.edu!newscon04.news.prodigy.net!prodigy.net!newsdst01.news.prodigy.net!prodigy.com!postmaster.news.prodigy.com!newssvr25.news.prodigy.net.POSTED!73fe1710!not-for-mail
From: "Bob Jones" <email@me.not>
Newsgroups: comp.databases.oracle.server
References: <1161031234.430942.187950@m7g2000cwm.googlegroups.com>   <iLUYg.18440$7I1.7767@newssvr27.news.prodigy.net>   <1161071595.908950@proxy.dienste.wien.at>   <B%cZg.15714$e66.4036@newssvr13.news.prodigy.com>   <1161128322.578292.108700@h48g2000cwc.googlegroups.com>   <cBeZg.14984$vJ2.1976@newssvr12.news.prodigy.com>   <1161162187.460298@proxy.dienste.wien.at>   <WnzZg.17687$6S3.2401@newssvr25.news.prodigy.net>   <1161242937.795839.104520@k70g2000cwa.googlegroups.com>   <nkVZg.12553$TV3.7139@newssvr21.news.prodigy.com> <1161323230.928976.262350@e3g2000cwe.googlegroups.com>
Subject: Re: serializable isolation level behavior question
Lines: 23
X-Priority: 3
X-MSMail-Priority: Normal
X-Newsreader: Microsoft Outlook Express 6.00.2900.2869
X-RFC2646: Format=Flowed; Original
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2962
Message-ID: <Y5d_g.18689$6S3.4049@newssvr25.news.prodigy.net>
NNTP-Posting-Host: 12.73.196.38
X-Complaints-To: abuse@prodigy.net
X-Trace: newssvr25.news.prodigy.net 1161387512 ST000 12.73.196.38 (Fri, 20 Oct 2006 19:38:32 EDT)
NNTP-Posting-Date: Fri, 20 Oct 2006 19:38:32 EDT
Organization: SBC http://yahoo.sbc.com
X-UserInfo1: [[PAPDONAJTORUPPBJK^OFXBWR\HPCTL@XT^OBPLAH[\BQUBLNTC@AWZWDXZXQ[K\FFSKCVM@F_N_DOBWVWG__LG@VVOIPLIGX\\BU_B@\P\PFX\B[APHTWAHDCKJF^NHD[YJAZMCY_CWG[SX\Y]^KC\HSZRWSWKGAY_PC[BQ[BXAS\F\\@DMTLFZFUE@\VL
Date: Fri, 20 Oct 2006 23:38:32 GMT
Xref: dp-news.maxwell.syr.edu comp.databases.oracle.server:277792


<hasta_l3@hotmail.com> wrote in message 
news:1161323230.928976.262350@e3g2000cwe.googlegroups.com...
>
> Bob Jones wrote :
>
>> <hasta_l3@hotmail.com> wrote in message
>> >
>> > The OP transaction performed casher DML statements.
>> > It had transaction level serializable.
>>
>> No, the session that was serializable was doing a truncate that is NOT a
>> DML.
>>
>
> Well, the way I read the OP description copied below,
> the serializable transaction (in session 2) issued only selects.
>
>

Okay, I got it backwards, but it still makes no difference to the argument.