On Wed, 14 May 2003, Adam Sherman wrote:
> How should one choose a Transaction Isolation Level?
So, read committed may return different data based on when you select, it,
while serializable will always return the same data. Further, concurrent
updates will not cause a read committed transaction to fail, but will
cause a serializable transaction to fail.
This means that in a read committed mode you MAY do an update on old data
that has changed in the database while you were running your transaction,
while serializable will fail and rollback it's transaction automatically,
thus forcing you to resubmit your transaction again.
This means read committed is easier to program in, but may result in some
data coherency issues, while serializable is more work, and tends to run
slower, but ensures your data is coherent as though each transaction ran
one at a time while all other transactions waited in line for it.
