transaction-isolation

I have MySQL Workbench (community-6.2.3) installed in a Ubuntu system using .deb. Workbench session does not seem to see updates (DML) to the database done by other sessions (applications/command line client). A new session is able to see correct status of the database at its start but non of the changes that happen afterwards is visible to it. It seems workbench session does sync up with db after a commit in workbench. I'm getting Error Code: 1412. Table definition has changed, please retry transaction when I try to query a table that I've created from a different session. Non workbench

With SQL Server's transaction isolation levels, you can avoid certain unwanted concurrency issues, like dirty reads and so forth. The one I'm interested in right now is lost updates - the fact two transactions can overwrite one another's updates without anyone noticing it. I see and hear conflicting statements as to which isolation level at a minimum I have to choose to avoid this. Kalen Delaney in her "SQL Server Internals" book says (Chapter 10 - Transactions and Concurrency - Page 592): In Read Uncommitted isolation, all the behaviors described previously, except lost updates , are possible

What is the difference between non-repeatable read and phantom read? I have read the Isolation (database systems) article from Wikipedia , but I have a few doubts. In the below example, what will happen: the non-repeatable read and phantom read ? Transaction A SELECT ID, USERNAME, accountno, amount FROM USERS WHERE ID=1 OUTPUT: 1----MIKE------29019892---------5000 Transaction B UPDATE USERS SET amount=amount+5000 where ID=1 AND accountno=29019892; COMMIT; Transaction A SELECT ID, USERNAME, accountno, amount FROM USERS WHERE ID=1 Another doubt is, in the above example, which isolation level

It is not entirely clear from MySQL documentation whether the InnoDB engine implements true serializable isolation 1 or snapshot isolation , which is often confusingly called "serializable" too. Which one is it? If MySQL InnoDB doesn't, are there any completely free, production-quality RDBMS which do? 1 where "true serializable isolation" means the absence of not only read anomalies as per the SQL standard, but also the write skew anomaly, explained in further detail here . regilero UPDATE: See comments, this seems to be fixed in MySQL 5.5 , with these examples we still have a table lock and