Mailing List
Home
Forum Home
MySQL General - General MySQL discussion
MySQL++ - Programming with the C++ API to MySQL
MaxDB - Everything about MaxDB, formerly known as SAP DB
ODBC - ODBC with the MySQL Connector/ODBC driver
MySQL on Win32 - Runing MySQL on Windows 9x/Me/NT/2000/XP
Java Help - Mostly related to the MySQL Connector/J driver
Perl - Perl support for MySQL with DBI and DBD::mysql
GUI - MySQL GUI Tools
Announcement
Subjects
mysql openssl Question
ERROR 1045: Access denied for user: 'root@localhost ' (Using
password: NO)
Update one field with more fields from another table
Getting Identity after INSERT
ERROR 2002: Can 't connect to local MySQL server through socket
mysql test 4 1 fails with the gis test
MySQL Cluster Software
Downgrade Mysql from 4 to 3 23
Mysql 4 0 Oracle Stored Procedure Trigger Conversion
Can 't access mysql after kernel upgrade
Executing MySQL Commands From Within C Program
Comparing and writing out BLOBS
Preventing Duplicate Entries
FULLTEXT query format question
Strange behavior, Table Level Permission
Does the binary log enabling affect the MySQL performances?
mysql:it 's a db not a dbms how it 's possible?!
mysql have same function mthod as Oracle decode()
 
Are transactions atomic?

Are transactions atomic?

2007-10-14       - By Baron Schwartz

 Back
Hi Douglas,

Douglas Pearson wrote:
> Sorry if this is a dumb question, but are SQL transactions in MySQL atomic?
> I'm using InnoDB tables in MySQL5.
>
> Clearly, transactions have the property that either all updates occur or
> none do.  By atomic, I mean are other queries guaranteed to either see all
> changes from the transaction or none of them?

You're actually asking about isolation -- the I in ACID.  yes, MySQL
transactions are ACID.  And MySQL and InnoDB implement all four levels
of transaction isolation described by the SQL standard.  Most RDBMSs
don't, so MySQL is actually a good bit more complicated to use correctly
with respect to transactions and isolation levels.

> An obvious example of the potential problem if they are not atomic (with
> regards to visibility):
>
> Transaction {
>   Query1 - update credits_table with +$20
>   Query2 - update debits_table with -$20
> }
>
> Separate process running periodically:
>   Query3 - compute total credits and debits
>
> Could query3 ever see the total of credits and debits as being out of
> balance?

Yes, if you choose the wrong isolation level.

> If the transaction doesn't guarantee that, is there any other way to force
> atomic visibility?

Choosing the right isolation level will do what you need.  It will not
guarantee no one can ever see inconsistent data, so if you're trying to
prevent people from being able to, you can't.  If you're trying to
design applications so they WON'T, you can do that.

You should read the section on InnoDB Transaction Model and Locking,
especially this section (but read the whole thing, it is very complex):
http://dev.mysql.com/doc/refman/5.0/en/innodb-transaction-isolation.html

Baron

--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe:    http://lists.mysql.com/mysql?unsub=mysql@(protected)