Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>A couple of possibilities spring to mind (no pun intended):</p> <p>a) Your JDBC driver defaults to autocommit=true and is somehow ignoring the beginTransaction() and rollback() calls;</p> <p>b) If you're using Spring 3, I <em>believe</em> that SessionFactory.getSession() returns the Hibernate Session object wrapped by a Spring proxy. The Spring proxy is set up on the Session in part to handle transaction management, and maybe it's possible that it is interfering with your manual transaction calls?</p> <p>While you can certainly use AOP-scoped proxies for transaction management, why not use the @Transactional(readOnly=false|true) annotation on your service layer methods? In your Spring config file for your service layer methods, all you need to do to make this work is to add </p> <pre><code>&lt;tx:annotation-driven /&gt; </code></pre> <p>See chapters 10 and 13 of the Spring Reference Documentation on Transaction Management and ORM Data Access, respectively:</p> <p><a href="http://static.springsource.org/spring/docs/3.0.x/reference/index.html" rel="nofollow">http://static.springsource.org/spring/docs/3.0.x/reference/index.html</a></p> <p>Finally, if you're using Spring 3, you can eliminate references to the Spring Framework in your code by injecting the Spring-proxied SessionFactory bean into your DAO code - no more need to use HibernateDaoSupport. Just inject the SessionFactory, get the current Session, and use Hibernate according to the Hibernate examples. (You can combine both HibernateDaoSupport and plain SessionFactory-based Hibernate code in the same application, if required.)</p>
    singulars
    1. This table or related slice is empty.
    1. POHibernateDaoSupport , transaction is not rolled back
      singulars
      1. PTQuestion
    1. PTAnswer
    1. This table or related slice is empty.
    1. USBobG
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. POHibernateDaoSupport , transaction is not rolled back
      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. VTUpMod
    3. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTAcceptedByOriginator
    1. COThe latter part of this is already addressed. I want to understand this *before* going into AOP or annotation based transactions.
      singulars
      1. PO
      1. USAnonym
    2. COb) is the only culprit I can think of as of now. I.e. there's some magic foo going on. In the end I've skipped the whole part and gone with the suggestion of AOP annotation based transaction management, getting rid of HibernateDaoSupport and injecting a LocalSessionFactoryBean directly in the DAO. Works fine.
      singulars
      1. PO
      1. USAnonym
 

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