Re: Drawbacks to Serializable Mode?

I had not heard this. I've been getting my information about isolation levels from the O8 manuals. Is there a document sowewhere stating this is the case? (not that I'm doubting you, I just have to support this to a team)
>- 8 obsoletes this setting in the init.ora, no long supported

This would certainly be bad, but seems to differ from from the Oracle manuals say. They say that a read never locks a table so others can't use it. The mechanism seems to be if Transaction A begins, then transaction B, and A updates a row read by B, then B will get an error if it tries to update the row. At least that's my understanding of it.
>- serializable = true causes a share table lock to be placed whenever you
READ a
>table (not so with serializable transactions using set transaction). This
>means, if you read a table with serializable=true -- no one can
>insert/update/delete it until you commit. slightly bad for concurrency.
Received on Fri Feb 26 1999 - 13:45:14 CST