The idea I generally use when working with transactions looks like this (semi-pseudo-code) :
try {
// First of all, let's begin a transaction
$db->begin();
// A set of queries ; of one fails, an exception should be thrown
$db->query('first query');
$db->query('second query');
$db->query('third query');
// If we arrive here, it means that no exception was thrown
// i.e. no query has failed ; and we can commit the transaction
$db->commit();
} catch (Exception $e) {
// An exception has been thrown
// We must rollback the transaction
$db->rollback();
}
Note that, with this idea, if a query fails, an Exception must be thrown :
- PDO can do that, depending on how you configure it
- else, with some other API, you might have to test the result of the function used to execute a query, and throw an exception yourself.
Unfortunately, there is no magic involved : you cannot just put an instruction somewhere and have transactions done automatically : you still have to specific which group of queries must be executed in a transaction.
For example, quite often, you'll have a couple of queries before the transaction (before the begin
), and another couple of queries after the transaction (after either commit
or rollback
) ; and you'll want those queries executed no matter what happened (or not) in the transaction.