Hibernate version:
3.1.3

Code between sessionFactory.openSession() and session.close():
Asset asset = new Asset();
asset.setAttribute("abc");
session.save(asset);

String hql = "from Asset as asset where asset.attribute=?";
List assets = session.createQuery(hql).setParameters(new String[] { "abc" }, new Type[] { new StringType() }).list();
Iterator it = assets.iterator();
if (it.hasNext()) {
Asset a = (Asset)it.next();
System.out.println(a.getAttribute());
} else {
throw new IllegalStateException("no data");
}

Name and version of the database you are using:
Oracle 10.2.0.2

In Hibernate 2.1.8, I use session.find() rather than query.list() but the otherwise identical code worked (it printed the attribute). After having followed the migration guide and upgraded to 3.1.3, I no longer get the result.

I turned on Hibernate logging and found that the INSERT statement occurs after the IllegalStateException has been thrown to the caller. It appears that Hibernate didn't call flush before list(). I tried session.setFlushMode(FlushMode.ALWAYS) but it didn't help; an explicit session.flush() before query.list() did.

Did I do something wrong? I don't want to call flush() after every save(). Worse, what about update (by calling setters)? Is there something obvious I missed?

Thanks
Kevin

By the way, session.load() can see the newly-inserted object. But query.list() still can't. Casting session to org.hibernate.classic.Session and using find() also doesn't work.

Are you not showing us the transaction in your code snippet or do you use CMT? The behavior you observed is normal. Hibernate waits as long as possible to execute the SQL insert statement unless you explicitly commit a transaction or execute a method like flush() on the session.

Try this code:



Grant

Hi Grant

Thanks for your reply. I understand how Hibernate delays pending updates to as late as possible - we depend critically on this feature for performance, as well as batching multiple updates into one if they are about the same table.

The documentation expressly said Query.list() will not return stale data nor will it return wrong data (10.10. Flushing the Session). I didn't show transaction code because all the code I showed belong to one transaction. I expect, in the same transaction, if I insert something I should be able to query it subsequently. This is consistent with SQL. Otherwise, it'd be stale or wrong data, wouldn't it? Anyway, the very same code works in Hibernate 2.1.8.

If I have to manually flush before every find it'd be a performance nightmare...

Kevin

Kevin, I can't comment further on the behavior you're observing without writing a test. I agree that a query done in the same transaction should return the updates and the Hibernate docs do state Query.list should never return stale or wrong data. My only other suggestion would be to try the latest 3.x release. It might be a bug in 3.1.

Grant