Re: Question about SERIALIZE transaction isolation

>> A transaction executing under the serializable transaction isolation level requires that every update by /other transactions/ be blocked if it might affect query results.  Updates that occur within a transaction /should/ be seen by subsequent queries within the same transaction. <<

As I remember it from my ANSI X3H2 days, everyone else got "kicked out of the DB" when there was a session with serializable transaction isolation level. The intent was not to allow any other concurrent transactions. This was how you could do physical file maintaining tasks on the WHOLE database. But we aleays added "effectively" to the definitions. Received on Fri Jun 19 2009 - 01:02:55 CEST