sinnombre00 wrote:
Hi. I found the same problem using Castle Project RC3 (nhibernate build 1.2.0.4000?) and IBM DB2 UDB running on iSeries/AS400.
We eventually fixed the problem. There were calls on our service layer that were transacted (default settings of the transaction annotation) when they should not have been. And because the entities in these calls were eventually updated inside the service, even though we did not call explicitly "update" on the entity manager, hibernate noticed the change and updated the DB. That had gone unnoticed to me.
A cleanup of the transaction declarations fixed the problem.