Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>The <code>@Transactional</code> defines the demarcation line. Annotating the class is equivalent with annotating each public method of the class, the line of demarcation is still the method (in your case, the <code>testNumberTransaction()</code>). The commit/rollback decision will be taken at the demarcation point, that is when returning from your test method. Regardless of whether you specify <code>REQUIRES</code> or <code>REQUIRES_NEW</code> propagation, the actual transaction unit is the same, your <code>testNumberTransaction()</code> method so the two <code>service.add(...)</code> calls will always be executed in the same transaction.</p> <p>If your goal is to always roll back your transactions after the test, then simply removing the <code>@Transactional</code> annotation (or putting @nontransactional as you mentioned) should do.</p> <p>If, on the other hand, you want to FORCE a new transaction for each <code>service.add(...)</code> invocation, you could either create a wrapper for your service class where you have an <code>add(...)</code> method that is annotated with @Transactional(propagation = Propagation.REQUIRES_NEW) and call the wrapped <code>service</code> instance <code>add(...)</code> method from there. OR you could add some declarative transaction management in your spring test context that adds transaction advise for your <code>service.add(...)</code> method. Read more in the <a href="http://static.springsource.org/spring/docs/2.5.x/reference/transaction.html#tx-propagation" rel="nofollow">spring documentation</a> on how to add declarative transaction support using the <code>&lt;tx:XXX&gt;</code> tags.</p>
    singulars
    1. This table or related slice is empty.
    1. POSpring tests inpact on service transactions
      singulars
      1. PTQuestion
    1. PTAnswer
    1. This table or related slice is empty.
    1. USpap
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    1. CORemoving @Transactional from the test method won't rollback the transaction: there won't be any transaction for the test. a transaction will start when the service method is called, and will commit when the service method returns.
      singulars
      1. PO
      1. USJB Nizet
    2. COTrue, clumsy formulation on my part. Removing the @Transactional annotation will prevent the transaction manager from creating a transaction in the java layer. Most databases will, however, always create an implicit transaction for each session and if you set auto-commit to off (which is default, IIRC), no transaction will behave the same way as transaction which always rolls back. Please correct me if I'm wrong.
      singulars
      1. PO
      1. USpap
    3. COErr, no. Removing the Transactional from the *test* method will make the test run outside of any transactional context, but Spring will still start a transaction for each service method call, since the *service* method is annotated with Transactional. The actual transactional work done by the service (which probably updates some database) will thus be done in a transaction and committed, unless the service itself throws a runtime exception.
      singulars
      1. PO
      1. USJB Nizet
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload