Two solutions for implementing MySQL nested transactions in PHP: mysql nested

Two solutions for implementing MySQL nested transactions in PHP: mysql nested

I. Problem Origin

MySQL official documentation clearly states that nested transactions are not supported:

1. Transactions cannot be nested. This is a consequence of the implicit commit timed Med for any current transaction when you issue a start transaction statement or one of its synonyms.

 

However, when developing A complex system, we will inevitably inadvertently embed transactions in the transaction. For example, function A calls function B and function A uses transactions, in addition, the B function is called in the transaction, and the B function also has a transaction, so that transaction nesting occurs. At this time, the transaction of A is of little significance. Why? As mentioned in the above document, the simple translation is:

1. When a start transaction command is executed, a commit operation is executed implicitly. Therefore, we need to support the nesting of transactions at the system architecture level.

 

Fortunately, nesting is supported in some mature ORM frameworks, such as doctrine or laravel. Next, let's take a look at how these two frameworks are implemented. Friendly reminder: The names of functions and variables in these two frameworks are relatively intuitive. Although they look very long, they can be directly known through the naming, so don't be scared as soon as you see it :)

 

Ii. doctrine Solution

 

First, let's take a look at the code for creating a transaction in doctrine (irrelevant code is eliminated ):

[Php]View plaincopy

1. /**
2. * Author http://www.lai18.com
3. * Date 2015-04-19
4. * Version 1
5. **/
6. Public function beginTransaction ()
8. {
10. + $ This-> _ transactionNestingLevel;
12. If ($ this-> _ transactionNestingLevel = 1 ){
14. $ This-> _ conn-> beginTransaction ();
16. } Else if ($ this-> _ nestTransactionsWithSavepoints ){
18. $ This-> createSavepoint ($ this-> _ getNestedTransactionSavePointName ());
20. }
22. }

 

The first line of this function uses a _ transactionNestingLevel to identify the current nested level. If it is 1, that is, it is not nested yet, then execute start transaction in the default method. If it is greater than 1, that is, when there is nesting, she will create a savepoint for us, this savepoint can be understood as a transaction record point. You can only roll back to this point when you need to roll back. Then let's look at the rollBack function:

 

[Php]View plaincopy

1. 1 ./**
2. * Author http://www.lai18.com
3. * Date 2015-04-19
4. * Version 1
5. **/
6. Public function rollBack ()
8. {
10. If ($ this-> _ transactionNestingLevel = 0 ){
12. Throw ConnectionException: noActiveTransaction ();
14. }
15. If ($ this-> _ transactionNestingLevel = 1 ){
17. $ This-> _ transactionNestingLevel = 0;
19. $ This-> _ conn-> rollback ();
21. $ This-> _ isRollbackOnly = false;
23. } Else if ($ this-> _ nestTransactionsWithSavepoints ){
25. $ This-> rollbackSavepoint ($ this-> _ getNestedTransactionSavePointName ());
27. -- $ This-> _ transactionNestingLevel;
29. } Else {
31. $ This-> _ isRollbackOnly = true;
33. -- $ This-> _ transactionNestingLevel;
35. }
37. }

 

We can see that the processing method is also very simple. If the level is 1, roll back directly; otherwise, roll back to the previous savepoint. Then let's continue to look at the commit function:

 

[Php]View plaincopy

1. 1 ./**
2. * Author http://www.lai18.com
3. * Date 2015-04-19
4. * Version 1
5. **/
6. Public function commit ()
8. {
10. If ($ this-> _ transactionNestingLevel = 0 ){
12. Throw ConnectionException: noActiveTransaction ();
14. }
16. If ($ this-> _ isRollbackOnly ){
18. Throw ConnectionException: commitFailedRollbackOnly ();
20. }
21. If ($ this-> _ transactionNestingLevel = 1 ){
23. $ This-> _ conn-> commit ();
25. } Else if ($ this-> _ nestTransactionsWithSavepoints ){
27. $ This-> releaseSavepoint ($ this-> _ getNestedTransactionSavePointName ());
29. }
30. -- $ This-> _ transactionNestingLevel;
32. }

 

Forget it. Let's just explain it :)

 

Iii. laravel's solution laravel's processing method is relatively simple and rough. Let's take a look at the operations for creating a transaction:

 

[Php]View plaincopy

1. 1.
2. /**
3. * Author http://www.lai18.com
4. * Date 2015-04-
5. * Version 1
6. **/
7. Public function beginTransaction ()
9. {
11. ++ $ This-> transactions;
12. If ($ this-> transactions = 1)
14. {
16. $ This-> pdo-> beginTransaction ();
18. }
20. }

 

How do you feel? So easy? First, judge how many transactions there are currently. If it is the first transaction, OK, the transaction starts. Otherwise, nothing will be done. Why is nothing done? Continue to the rollBack operation:

 

[Php]View plaincopy

1. 1 ./**
2. * Author http://www.lai18.com
3. * Date 2015-04-19
4. * Version 1
5. **/
6. Public function rollBack ()
8. {
10. If ($ this-> transactions = 1)
12. {
14. $ This-> transactions = 0;
15. $ This-> pdo-> rollBack ();
17. }
19. Else
21. {
23. -- $ This-> transactions;
25. }
27. }

 

Do you understand? The rollback is true only when the current transaction has only one transaction; otherwise, the count is only subtracted by one. This is why laravel's processing is relatively simple and crude. In the nested inner layer, there is actually a real transaction, and only the outermost layer is a whole transaction. Although it is simple and crude, but it also solves the commit problem when creating a transaction in the internal layer. The principle is like this. For the sake of completeness, copy the commit code!

 

[Php]View plaincopy

1. Public function commit ()
3. {
5. If ($ this-> transactions = 1) $ this-> pdo-> commit ();
6. -- $ This-> transactions;
8. }