Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>From <a href="http://static.springsource.org/spring/docs/2.0.x/reference/transaction.html" rel="noreferrer">http://static.springsource.org/spring/docs/2.0.x/reference/transaction.html</a></p> <blockquote> <p><strong>The Spring team's recommendation is that you only annotate concrete classes with the <code>@Transactional</code> annotation, as opposed to annotating interfaces.</strong> You certainly can place the <code>@Transactional</code> annotation on an interface (or an interface method), but this will only work as you would expect it to if you are using interface-based proxies. The fact that annotations are <em>not inherited</em> means that if you are using class-based proxies then the transaction settings will not be recognised by the class-based proxying infrastructure and the object will not be wrapped in a transactional proxy (which would be decidedly <em>bad</em>). So please do take the Spring team's advice and only annotate concrete classes (and the methods of concrete classes) with the <code>@Transactional</code> annotation.</p> <p><em>Note: Since this mechanism is based on proxies, only 'external' method calls coming in through the proxy will be intercepted.</em> This means that 'self-invocation', i.e. a method within the target object calling some other method of the target object, won't lead to an actual transaction at runtime even if the invoked method is marked with <code>@Transactional</code>!</p> </blockquote> <p>(Emphasis added to the first sentence, other emphasis from the original.)</p>
    singulars
    1. This table or related slice is empty.
    1. POWhere should I put @Transactional annotation: at an interface definition or at an implementing class?
      singulars
      1. PTQuestion
    1. PTAnswer
    1. UST.J. Crowder
    1. USRomain Hippeau
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. POWhere should I put @Transactional annotation: at an interface definition or at an implementing class?
      singulars
      1. PTQuestion
    1. This table or related slice is empty.
    1. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTAcceptedByOriginator
    3. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    1. COBig +1 BTW, I took the liberty of making the quote a quote, so people aren't confused, and added back the italics and such from the original.
      singulars
      1. PO
      1. UST.J. Crowder
    2. CO@T.J. Crowder - Amazing how other answers change. thx, NP
      singulars
      1. PO
      1. USRomain Hippeau
    3. COI have read this statement before in Spring docu, but still I cannot understand why _transaction settings will not be recognised by the class-based proxying infrastructure_? I personally think, this is just Spring implementation limitation, not the problem of underlying proxy infrastructure.
      singulars
      1. PO
      1. USdma_k
 

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