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
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
BTW, I started a design proposal wiki for this work:
https://github.com/hibernate/hibernate-orm/wiki/6.0-persister-redesign
ATM this is very basic initial thoughts.
On Sat, Jul 16, 2016 at 7:55 AM Steve Ebersole wrote:
> Along with the Type redesign in 6.0 we will need to do some redesigning of
Along with the Type redesign in 6.0 we will need to do some redesigning of
the persister contracts. I'd like to start collaborating on those changes
with the ongoing 6.0 wip work. I plan on having a design meeting in the
"Hibernate ORM" HipcHat room on Monday around 12 pm Central US time for
anyo
