А>>оракл в точности соответствует ANSI (там нет требований упорядовачивать по коммиту), иначе бы их не пустили на tpc.org
M>На что спорим?
на статью по эскалации давай в это оригинальное решение добавим мелкими буквами не оригинальное оракловое

http://www.tpc.org/results/FDR/TPCC/hp_tpcc_rx5670_fdr.pdf

6.6.4 Serializable Transactions
Oracle supports serializable transaction isolation in full compliance with the SQL92 and TPC-C requirements. This is
implemented by extending the multiversity concurrency control mechanism long supported by Oracle.
Oracle queries take no read locks and see only data committed as of the beginning of the query's execution. This
means that readers and writers coexist without blocking one another, providing a high degree of concurrency and
consistency. While this mode does prevent reading dirty data, Oracle's default isolation level also permits a transaction
that issues a query twice to see non-repeatable reads and phantoms, as defined in SQL92 and TPC-C.
Beginning with Oracle7 release 7.3, a transaction may request a high degree of isolation with the command SET
TRANSACTION ISOLATION LEVEL SERIALIZABLE, as defined in SQL92.

стр. 36
©Copyright Hewlett-Packard Company 2003

Gt_