Re: Transactions: good or bad?

> > Is deadlock a system failure?

Writing a single var atomically is not enough. If you try to write 100 values atomically, like, you have a super update statement, you will still have deadlocks because all 100 rows will have to have read and write isolation internally.

If you have, in your model, two competing UPDATE statements, and, there is an intersection of the rows they are updating, then, you can still have a deadlock.

The problem of deadlocks cannot be solved by assuming an atomic assignment of multiple values of once - atomic assignment of multiple values is exactly what a transaction is, and that causes deadlocks.

So, you have to have deadlock detection scheme in your code anyway. It seems silly to have the users of your system use TWO deadlock detection schemes, the one you propose and the one you have to have.

Of course, you can serialize based on TABLE - or do TABLE level locking, in otherwords, and that could make your atomic assignment work. But, congratulations, you've just rewritten MYSQL. Received on Mon May 19 2003 - 14:28:09 CEST