Re: Avoiding any locks in SQL Servers - read and understand....its magic.

"Heikki Tuuri" <Heikki.Tuuri_at_innodb.com> writes:

>> This transaction cannot be guaranteed to execute in a serializable
>> order, even though you have chosen the 'serializable' isolation
>> level.

>MySQL/InnoDB IS an industrial-strength transaction processing
>DBMS. Wonder when Oracle and PostgreSQL catch up ;).

Well, you can get true serializability and ACID for all transactions, without question, by using a single-threaded database engine and executing only one transaction at a time. The difficulty comes in getting concurrent access and integrity as well...

(Not saying that InnoDB does this - just pointing out that safety properties are only half of the requirement, you must count performance too.)

-- 
Ed Avis <ed_at_membled.com>