Hibernate Community • View topic - session.flush() vs transaction.commit()

View unanswered posts | View active topics

Board index » Hibernate & Java Persistence » Hibernate Users

All times are UTC - 5 hours [ DST ]

session.flush() vs transaction.commit()

Page 1 of 1

[ 3 posts ]

Previous topic | Next topic

Author

Message

haisony

Post subject: session.flush() vs transaction.commit()

Posted: Fri May 11, 2012 12:19 pm

Newbie

Joined: Fri May 11, 2012 10:49 am
Posts: 3

What is the impact of flush() on other transactions, if called before commit() on a given transaction?
Can DB transactions, stored procedures view flushed changes before commit()?

Top

haisony

Post subject: Re: session.flush() vs transaction.commit()

Posted: Tue May 15, 2012 2:21 am

Newbie

Joined: Fri May 11, 2012 10:49 am
Posts: 3

Surprised no answers after so many days :(
Am I posting at wrong place? Please advice me.

Top

nordborg

Post subject: Re: session.flush() vs transaction.commit()

Posted: Tue May 15, 2012 3:12 am

Expert

Joined: Wed Mar 03, 2004 6:35 am
Posts: 1240
Location: Lund, Sweden

If another transaction can see uncommited changes depends on the transaction isolation level of the other transaction. For a good explanation of this see for example wikipedia: http://en.wikipedia.org/wiki/Isolation_ ... systems%29

You should also be aware of that not all databases support all isolation levels.

Top

Page 1 of 1

[ 3 posts ]

Board index » Hibernate & Java Persistence » Hibernate 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