I assume "...but when I change a field of a db-record manually..." means you go into the database and tweak a field?
In which case this is definitely a hibernate session usage issue and I'd suggest you read up on the latter. With kind regards, Mike -----Original Message----- From: rules-users-boun...@lists.jboss.org [mailto:rules-users-boun...@lists.jboss.org] On Behalf Of Thomas Zwifl Sent: 10 July 2009 11:46 To: rules-users@lists.jboss.org Subject: [rules-users] Hibernate Query delivers wrong values Hi there! I'm working with the latest snapshot-releas of v5.1 (build3098-rev27324-20090630-0403). My application consists of two independent processes, both are repeated periodically (timer-node). the processes both have ruleset-nodes. some rules are querying a database with hibernate in the rule condition (LHS). the queried objects are then inserted into workinmemory (insert(object)), then some computation follows, the objects are modified and written back to db, and then the objects are retracted (retract(object)). Now to the problem: when I start the application, everything works correct, and leads to the right results. But when I change a field of a db-record manually, the hibernate-query delivers the old values!! (of course the changes are committed.) Anyone has an idea whats going wrong here? Is there some kind of caching mechanism that delivers the old objects instead of querying the database? greetz! tom -- GRATIS für alle GMX-Mitglieder: Die maxdome Movie-FLAT! Jetzt freischalten unter http://portal.gmx.net/de/go/maxdome01 _______________________________________________ rules-users mailing list rules-users@lists.jboss.org https://lists.jboss.org/mailman/listinfo/rules-users _______________________________________________ rules-users mailing list rules-users@lists.jboss.org https://lists.jboss.org/mailman/listinfo/rules-users
