Will Hibernate flush my updated persistent object when calling session.close()(using FlushMode.AUTO)?

No it won't, and you should use a transaction with well defined boundaries Quoting Non-transactional data access and the auto-commit mode.

Will bernate flush my updated persistent object when calling session.close() (using FlushMode. AUTO)? No it won't, and you should use a transaction with well defined boundaries.

Quoting Non-transactional data access and the auto-commit mode: Working nontransactionally with bernate Look at the following code, which accesses the database without transaction boundaries: Session session = sessionFactory.openSession(); session. Get(Item. Class, 123l); session.close(); By default, in a Java SE environment with a JDBC configuration, this is what happens if you execute this snippet: A new Session is opened.It doesn’t obtain a database connection at this point.

The call to get() triggers an SQL SELECT. The Session now obtains a JDBC Connection from the connection pool.By default, immediately turns off the autocommit mode on this connection with setAutoCommit(false). This effectively starts a JDBC transaction!

The SELECT is executed inside this JDBC transaction. The Session is closed, and the connection is returned to the pool and released by bernate — bernate calls close() on the JDBC Connection. What happens to the uncommitted transaction?

The answer to that question is, “It depends! €? The JDBC specification doesn’t say anything about pending transactions when close() is called on a connection.

What happens depends on how the vendors implement the specification. With Oracle JDBC drivers, for example, the call to close() commits the transaction! Most other JDBC vendors take the sane route and roll back any pending transaction when the JDBC Connection object is closed and the resource is returned to the pool.

Obviously, this won’t be a problem for the SELECT you’ve executed, but look at this variation: Session session = getSessionFactory().openSession(); Long generatedId = session. Save(item); session.close(); This code results in an INSERT statement, executed inside a transaction that is never committed or rolled back. On Oracle, this piece of code inserts data permanently; in other databases, it may not.

(This situation is slightly more complicated: The INSERT is executed only if the identifier generator requires it. For example, an identifier value can be obtained from a sequence without an INSERT. The persistent entity is then queued until flush-time insertion — which never happens in this code.

An identity strategy requires an immediate INSERT for the value to be generated. ) Bottom line: use explicit transaction demarcation.

I just finished this passage from the link you gave me in another question to return here, refresh and see it. You are of course correct and thank you very much for clarifying this important topic for me. – Ittai Oct 14 '10 at 9:07 upvoted your anwser :) – Salandur Oct 14 '10 at 9:15.

Closing a session will always flush al work to the database. Flushmode. AUTO flushes work to the database when there are changes and you are quering the table with changed records.

Thanks for your answer. Can you attach some sort of reference to this statement? I've read two many postings on-line regarding this which confuse me (hence my question) and I'd appreciate a link to a certified – Ittai Oct 14 '10 at 8:10 docs.jboss.Org/hibernate/stable/core/reference/en/html/… ok I was not entirely correct.

If you are using transactions, the commit will flush. If there is no active transaction, all changes are directly propagated to the database (a transaction per session-method call) – Salandur Oct 14 '10 at 8:16 1 This is incorrect. – Pascal Thivent Oct 14 '10 at 9:05 true, since my experience is unfortunatly with oracle 9 database – Salandur Oct 14 '10 at 9:16.

I cant really gove you an answer,but what I can give you is a way to a solution, that is you have to find the anglde that you relate to or peaks your interest. A good paper is one that people get drawn into because it reaches them ln some way.As for me WW11 to me, I think of the holocaust and the effect it had on the survivors, their families and those who stood by and did nothing until it was too late.