Spring中的事务级别required的解释

2019独角兽企业重金招聘Python工程师标准>>>

Spring中的事务级别required的解释：

When the propagation setting is PROPAGATION_REQUIRED, a logical transaction scope is created for each method upon which the setting is applied. Each such logical transaction scope can determine rollback-only status individually, with an outer transaction scope being logically independent from the inner transaction scope. Of course, in case of standard PROPAGATION_REQUIRED behavior, all these scopes will be mapped to the same physical transaction. So a rollback-only marker set in the inner transaction scope does affect the outer transaction's chance to actually commit (as you would expect it to).

 

If you need a laymans explanation of the use beyond that provided in the Spring Docs

Consider this code...

class Service {

    @Transactional(propagation=Propagation.REQUIRED)

    public void doSomething() {

        // access a database using a DAO

    }

}

 

 

      When doSomething() is called it knows it has to start a Transaction on the database before executing. If the caller of this method has already started a Transaction then this method will use that same physical Transaction on the current database connection.

This @Transactional annotation provides a means of telling your code when it executes that it must have a Transaction. It will not run without one, so you can make this assumption in your code that you wont be left with incomplete data in your database, or have to clean something up if an exception occurs.

Transaction management is a fairly complicated subject so hopefully this simplified answer is helpful

转载于:https://my.oschina.net/iioschina/blog/908391