Second-level cache entity "evict" when having two entities (mapped) representing the same DB row.
-------------------------------------------------------------------------------------------------
Key: HHH-1841
URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-1841
Project: Hibernate3
Type: Improvement
Versions: 3.1.3
Environment: Hibernate 3.1.3 & MySQL 4.1.x (unimportant)
Reporter: Karol Bucek
Priority: Minor
This is "simple" to understand, I am not sure if it makes sense to handle this in Hibernate.
Let's propose we have two different entites A and B (extends A) mapped over the same DB table (using polymorphism="explicit") thus having a "light" representation of the data in the table. Now if the second-level cache is enabled (we are caching A instances) and Hibernate performs an update(B) operation while the "same" A (meaning with the same identifier thus representing the same row) was cached before, the A instance will stay in the cache and thus will represent the "old" data until it expires (old is evicted by hand using the SessionFactory).
--
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.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
|
