Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 69.92%. Comparing base (1b63dd0) to head (63539f6).
⚠️ Report is 1 commits behind head on 2.x.

@@             Coverage Diff              @@
##                2.x    #7708      +/-   ##
============================================
- Coverage     69.94%   69.92%   -0.02%     
+ Complexity      994      992       -2     
============================================
  Files          1322     1322              
  Lines         50177    50175       -2     
  Branches       5932     5932              
============================================
- Hits          35095    35084      -11     
- Misses        12144    12157      +13     
+ Partials       2938     2934       -4     

PRs need to be registered, and the title must clearly describe the change — not just be an issue link.

done

如下测试场景通过
1、pg数据库，加上@GlobalTransactional，正常提交事务成功。
2、pg数据库，加上@GlobalTransactional，报错回滚成功。
3、pg数据库，加上@GlobalTransactional，超时回滚成功。
4、pg数据库，加上@GlobalTransactional和@transactional注解，正常提交事务成功。
5、pg数据库，加上@GlobalTransactional和@transactional注解，报错回滚成功。
6、pg数据库，加上@GlobalTransactional和@transactional注解，超时回滚成功。
7、mysql5.7数据库，加上@GlobalTransactional，正常提交事务成功。
8、mysql5.7数据库，加上@GlobalTransactional，报错回滚成功。
9、mysql5.7数据库，加上@GlobalTransactional，超时回滚成功。
10、mysql5.7数据库，加上@GlobalTransactional和@transactional注解，正常提交事务成功。
11、mysql5.7数据库，加上@GlobalTransactional和@transactional注解，报错回滚成功。
12、mysql5.7数据库，加上@GlobalTransactional和@transactional注解，超时回滚成功。
The following test scenarios passed successfully:

1. In the PostgreSQL database, adding the @GlobalTransactional annotation resulted in a successful, normal transaction commit.
2. Again in the PostgreSQL database, applying @GlobalTransactional led to an error, but the rollback was executed successfully.
3. Still in PostgreSQL, when @GlobalTransactional was combined with a timeout setting, the rollback occurred as expected.
4. In the PostgreSQL database, using both @GlobalTransactional and the @Transactional annotation allowed for a successful, normal transaction commit.
5. In PostgreSQL, combining @GlobalTransactional with @Transactional triggered an error, yet the rollback proceeded without issues.
6. Once more in PostgreSQL, integrating @GlobalTransactional along with @Transactional and introducing a timeout caused the rollback to complete successfully.
7. In the MySQL 5.7 database, adding the @GlobalTransactional annotation resulted in a successful, normal transaction commit.
8. In MySQL 5.7, incorporating @GlobalTransactional led to an error, but the rollback was handled successfully.
9. Also in MySQL 5.7, when @GlobalTransactional was used alongside a timeout, the rollback completed as expected.
10. In the MySQL 5.7 database, employing both @GlobalTransactional and @Transactional annotations enabled a successful, normal transaction commit.
11. In MySQL 5.7, combining @GlobalTransactional with @Transactional caused an error, though the rollback was still executed successfully.
12. Finally, in MySQL 5.7, using @GlobalTransactional with @Transactional and a timeout setting resulted in a successful rollback.