MySQL looks at many SQL operations differently depending on the MySQL storage engine currently in use. A given bit of code may (and often does) behave differently when it is executed against a different storage engine.
The default configuration of MySQL (as it is delivered when first installed) uses MyISAM, which does not support the concept of transactions at all, so there is no issue of ATOMIC or otherwise. If you read the MySQL manual
COMMIT section, you'll find a single sentence that gives the key tidbit that you need:
Quote:
|
Originally Posted by MySQL Manual
If you are using a transaction-safe storage engine (such as InnoDB, BDB, or NDBCLUSTER), you can disable autocommit mode with the following statement:
|
Follow the link that r937 gave you, and read carefully. The information that you need is there. Read it carefully and interpret the manual
very literally... The manual is almost always correct, especially when you think that it must be kidding!
-PatP