Re: serializable isolation level behavior question

"Laurenz Albe" <invite_at_spam.to.invalid> wrote in message news:1161162187.460298_at_proxy.dienste.wien.at...
>
> A serializable transaction must not get different results when issuing
> the
> same query twice. Period.
>
> This must hold, no matter what any other transaction does, and
> irrespective
> of that other transaction's isolation level.
>
> To be standard compliant, you must maintain serializability even if
> somebody else does a DROP TABLE or TRUNCATE TABLE.
> The fact that TRUNCATE is not part of the SQL standard has no
> implications
> in this case!
>

The TRUNCATE looks like a case of "no-one thought of that one". I'd raise an SR with Oracle with the argument that it's returning the wrong result - that's always a high priority. They may, of course, give you the workaround that you should 'delete table' regardless of the performance impact.

I'm not sure that you're right about there being a requirement for serialisability being maintained across a schema change though,

-- 
Regards

Jonathan Lewis
http://www.oracle.com/technology/community/oracle_ace/ace1.html#lewis

The Co-operative Oracle Users' FAQ
http://www.jlcomp.demon.co.uk/faq/ind_faq.html

Cost Based Oracle: Fundamentals
http://www.jlcomp.demon.co.uk/cbo_book/ind_book.html