James Holmes wrote: > That's what I thought, but I got different behaviour in my testing (the > behaviour I saw is supported by the docs, which I'll quote in a bit). I > started two separate transactions (read committed, the default) (call > them 1 and 2); inserted in 1, inserted in 2, select max in both, each > returns the correct id; commit 2 - now select max in 1 returns the > incorrect higher result from the committed 2.
> "Oracle meets the READ COMMITTED isolation standard. This is the default > mode for all Oracle applications. Because an Oracle query only sees data > that was committed at the beginning of the query (the snapshot time), > Oracle actually offers more consistency than is required by the ANSI/ISO > SQL92 standards for READ COMMITTED isolation." - Again note that this is > for one query (statement), not one transaction, I always thought Oracle took a snapshot at the beginning of the transaction and didn't forward it anymore but only applied local changes. I guess it is smarter then that :-) Jochem ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Discover CFTicket - The leading ColdFusion Help Desk and Trouble Ticket application http://www.houseoffusion.com/banners/view.cfm?bannerid=48 Message: http://www.houseoffusion.com/lists.cfm/link=i:4:208659 Archives: http://www.houseoffusion.com/cf_lists/threads.cfm/4 Subscription: http://www.houseoffusion.com/lists.cfm/link=s:4 Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=11502.10531.4 Donations & Support: http://www.houseoffusion.com/tiny.cfm/54
