DevShed.com has a new article posted - the second in a series of using those powerful little tools in MySQL, transactions.

In Using Transactions In MySQL (Part 2), they build on the foundation that they created in part 1 (see here). They note that most of that article was written assuming that it was a single user performing the updates/deletes/adds. So, part 2 deals more with the multi-user aspect of things, including some talk about possible data corruption issues. The isolation of transactions between users helps, but it can't always be relied upon. Instead, they show things like "the three Rs" and what your database admin can do to help keep things clean.

They continue on to talk about table locking and how it can help keep other clients in a "holding pattern" before it allows them to change any data. They even mention the binary log way to help you ensure that your MySQL data isn't corrupted in the event of a system failure. And, of course, they wrap it all up with a code example, showing how these transactions can work with a simple Perl script.