After thinking about our discussions some more, I wonder if it is not
better to simply have the persister and Type be the same for entity,
collection and embeddable. Assuming we do not separate "persister" and
"metadata" I think this is the way to go.
Thoughts?
On Mon, Jul 18, 2016 at 6:24 AM S
This is the comment that will now be added to an issue whenever an issue is
transitioned to "Awaiting Test Case":
Please attach a short but complete [test case|
https://github.com/hibernate/hibernate-orm/wiki/Test-Case-Guide] that
reproduces the reported bug.
* That Test Case Guide is something I
Hi Steve,
a (long) while back we had a "design chat" session which might be
related; I was then asking if it was possible to break up the
persistence context, which is today essentially one map containing all
entries even for different types, and break that up into multiple
smaller maps, one per P
Hi Vlad,
I think that might be quite tricky to implement, as it might not
always be clear into which region we'd need to lookup from, or
invalidate, not least locks might need to cross multiple regions.
Think for example when a type A is removed with ID=1, and then a type
B with the same ID is bei
Hi,
I bumped into this question on our forum:
https://forum.hibernate.org/viewtopic.php?f=1&t=1043470
And after I tried an example using the latest Hibernate version I see that,
for inheritance, all subentities share the parent region name.
This can be found in org.hibernate.internal.CacheImpl
