Multi-transaction usage pattern

unkyaku · **Joined:** Wed Oct 01, 2003 11:01 pm **Posts:** 23

What is the proper usage pattern for multiple transactions in a session?

Is it:

Code:

session = sessionFactory.getSession();
transaction = session.beginTransaction();
... some stuff ...
transaction.commit();
... some stuff ...
transaction.commit();
session.close();

Or:

Code:

session = sessionFactory.getSession();
transaction = session.beginTransaction();
... some stuff ...
transaction.commit();
transaction = session.beginTransaction();
... some stuff ...
transaction.commit();
session.close();

Thanks,
-Mark

firelord · **Joined:** Fri Jul 16, 2004 6:22 pm **Posts:** 17

I'm new to Hibernate, but for some reason I was under the impression that transactions were supposed to used 1 to 1 with a session. In other words, a new session should be created per transaction. This view could certainly be wrong, and if it is, someone please correct me.

christian · **Posted:** Fri Jul 16, 2004 7:24 pm

No, there are several patterns. The Session acts as a "persistence context", this is useful for long running "application transactions". There is a page on the Wiki/Community Area that describes the session and transaction scopes. If you need more detaild information about application design with a persistence context, read Hibernate in Action.

unkyaku · **Joined:** Wed Oct 01, 2003 11:01 pm **Posts:** 23

Christian, I've read the wiki page but it does not answer my question. Perhaps I've mislabeled my message, but all I'm asking for is if I need to start a new transaction after every commit, or if I can just keep working in the current transaction.

Thanks.

mchyzer · **Joined:** Sat Jul 17, 2004 5:16 pm **Posts:** 143

unkyaku wrote:

Christian, I've read the wiki page but it does not answer my question. Perhaps I've mislabeled my message, but all I'm asking for is if I need to start a new transaction after every commit, or if I can just keep working in the current transaction.

Thanks.

Are you trying to save 1 line of code, or are you just trying to write Java like you would sql, or is there another reason? Whether you can save this line or not, I would keep it in (start a new transaction). Based on the API, even if it happens to work now without starting a transaction, I would think you are safer to start it anyway in case things change in future releases of Hibernate (someone correct me if Im wrong, I didnt check the source code):

http://www.hibernate.org/hib_docs/api/n ... ml#commit()

http://www.hibernate.org/hib_docs/api/n ... ansaction()

Chris

mchyzer · **Joined:** Sat Jul 17, 2004 5:16 pm **Posts:** 143

firelord wrote:

I'm new to Hibernate, but for some reason I was under the impression that transactions were supposed to used 1 to 1 with a session. In other words, a new session should be created per transaction. This view could certainly be wrong, and if it is, someone please correct me.

This is definitely wrong. Check here for many design strategies on transactions and sessions:

http://www.hibernate.org/168.html

What you describe is one option if it is conducive to your app, but you dont have to do it that way...

Chris

gavin · **Posted:** Mon Jul 19, 2004 3:40 pm

Get Hibernate in Action, this stuff is a main theme of the book.