-->
These old forums are deprecated now and set to read-only. We are waiting for you on our new forums!
More modern, Discourse-based and with GitHub/Google/Twitter authentication built-in.

All times are UTC - 5 hours [ DST ]



Forum locked This topic is locked, you cannot edit posts or make further replies.  [ 2 posts ] 
Author Message
 Post subject: Consequences of not commiting transaction
PostPosted: Mon Oct 22, 2007 7:19 am 
Senior
Senior

Joined: Mon Jul 24, 2006 8:43 am
Posts: 160
Hi,
I am using an application managed entity manager.
I am just wondering what (if any) are the consequences of not committing a transaction that has been begun?

Code:
entityManager.getTransaction().commit();
// perform other entityManager operations


There's the obvious the data will not be committed to the database, but I am just thinking is there anything else.
Appreciate it's an odd question as this is something that is obviously not recommended, I would still like to know if there are any other consequences.
Rgds


Top
 Profile  
 
 Post subject:
PostPosted: Tue Oct 23, 2007 1:20 pm 
Hibernate Team
Hibernate Team

Joined: Sun Sep 14, 2003 3:54 am
Posts: 7256
Location: Paris, France
Actually with Oracle, your data will be committed. So you'd better rollback explicitly

_________________
Emmanuel


Top
 Profile  
 
Display posts from previous:  Sort by  
Forum locked This topic is locked, you cannot edit posts or make further replies.  [ 2 posts ] 

All times are UTC - 5 hours [ DST ]


You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum

Search for:
© Copyright 2014, Red Hat Inc. All rights reserved. JBoss and Hibernate are registered trademarks and servicemarks of Red Hat, Inc.