Hibernate Community • View topic - When to use Transaction API instead of simple Flush()?

View unanswered posts | View active topics

Board index » Hibernate & Java Persistence » NHibernate Users

All times are UTC - 5 hours [ DST ]

When to use Transaction API instead of simple Flush()?

Page 1 of 1

[ 3 posts ]

Previous topic | Next topic

Author

Message

DavidMartines

Post subject: When to use Transaction API instead of simple Flush()?

Posted: Tue Jul 31, 2007 1:11 pm

Newbie

Joined: Tue Jul 31, 2007 1:00 pm
Posts: 2

Hi, I'm sure this has been answered before but I can't seem to find any clear answer. As I understand it, a call to ISession.Flush() will execute any insert/update/delete statements within a transaction, so that if one fails all are rolled back. In what situation would I actually need to start my own transaction and use the Comit()/Rollback() methods, rather than just using Flush() and having the transaction handled automatically?

Thanks

Top

merge_s.rottem

Post subject:

Posted: Tue Jul 31, 2007 1:35 pm

Expert

Joined: Tue Aug 23, 2005 5:52 am
Posts: 335

Transactions are not started unless you explicitly start them. A flush is not atomic unless you have created a transaction first.

Symon.

Top

DavidMartines

Post subject:

Posted: Tue Jul 31, 2007 2:13 pm

Newbie

Joined: Tue Jul 31, 2007 1:00 pm
Posts: 2

Oh, ok. I thought flush was Atomic. Good to know.

Thanks

Top

Page 1 of 1

[ 3 posts ]

Board index » Hibernate & Java Persistence » NHibernate Users

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