[hibernate-issues] [Hibernate-JIRA] Commented: (HHH-2350) 2nd level cache broken for non-inverse bidirectional one-to-many relation

[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-2350?page=c... ] Gail Badner commented on HHH-2350: ---------------------------------- Here is what is happening: 1) The many-to-one association is (correctly) mapped with update="false" 2) PropertyFactory.buildStandardProperty(...) indicates that the many-to-one association is not dirty-checkable, unless the many-to-one association is mapped with not-found="ignore". (It passes alwaysDirtyCheck || property.isUpdateable() to the StandardProperty constructor; alwaysDirtyCheck is false unless not-found="ignore"). 3) When the entity with an update to the many-to-one association is flushed, TypeFactory.findDirty(...) does not dirty-check the association because the following is false: final boolean dirty = currentState[i] != LazyPropertyInitializer.UNFETCHED_PROPERTY && properties[i].isDirtyCheckable( anyUninitializedProperties ) && properties[i].getType().isDirty( previousState[i], currentState[i], includeColumns[i], session ); 4) The many-to-one association is (correctly) updated in the DB when the dirty non-inverse collection is updated by CollectionUpdateAction, which evicts the collection from the second-level cache 5) EntityUpdateAction is responsible for updating/removing a modified entity from the cache. Since the entity is not dirtied by other updated properties, an EntityUpdateAction is not created, and so the unmodified entity remains in the cache. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://opensource.atlassian.com/projects/hibernate/secure/Administrators.... - For more information on JIRA, see: http://www.atlassian.com/software/jira