Recently we debugged an issue where Hibernate 3.2 was storing automatically before a query because the object in question had 'dirty' properties (changed in RAM but not stored yet).

I understand this is expected behavior under some criteria, in order to keep objects in sync, but there isn't much documentation I can find besides a FAQ reference (search for 'dirty') to describe it.

So far, I can't replicate the behavior in a test case.

Is there a test case somewhere that causes an automatic store before query because of 'dirty' properties? Or can you describe how to write such a test case?

thanks,

larry