Upgrading from Hibernate 2.1 beta 6 to 2.1 rc1 causes more exceptions like this one to occur:


These new exceptions cause problems, when they propagate into my application.

Do you have some idea what changed in Hibernate? What I can do about it? (I am trying to figure it out on my own, of course.)

It appears that Hibernate 2.1 rc1 (and 2.1 final) flush more frugally; that is, they don't flush changes to the database in situations wherein previous releases would flush changes. This is an improvement, I trust. But it exposed a bug in my application: my code was implicitly relying on the extra flush to insert a row into the database, which causes the execution of a trigger which inserts other rows, which my application expects to load from the database via Hibernate. When the flush didn't happen, the attempt to load from the other rows failed with ObjectNotFoundException.

I changed my application to call Session.flush() before attempting to load the other rows, with satisfactory results.

I don't recall making any changes here.

Exactly what what was the code?

I looked at DEBUG log output, comparing logs from 2.1beta6 to logs from 2.1rc1, and saw flush activity in the former but not the latter (under similar circumstances). But I don't understand the Hibernate code well enough to identify the change therein.

My application is rather large and not open source. So I can't share its code with you, I'm sorry to say. :-(

Could you just try and verify that the flush was not required for the query that was executed? I'm certain this stuff is implemented correctly, but I'm very surprised to see a change in behavior....


Hibernate should flush if there are in-memory changes to a table that appears in the where clause (or order by or group by clause) of the query.

Yes, Hibernate 2.1 beta 6 executed a flush that was not required by a subsequent query (that I can see). The flush executed a SQL "insert into DRDomainMembership", and then Hibernate returned control to the application without executing a SQL query that mentioned DRDomainMembership.

Hrrrmph ... ok then, cool.

Must have changed something after all.....

Actually, by inserting a row into a table, say table Albert. This table is emptied. Then I try to use a different DB user and doing the same thing, a new table Albert is created by this new user.

By retrieving a row from the table, the table is emptied.

Something is really wrong with this.

Later on, I use hibernate version 2.0.3, everything works fine with a single line of code change. So I think there is serious problem with the current 2.1.2 release.

Thanks,
John