Hello Steve, as you asked moving our discussion about HHH-7572 in dev mail
list.
Regarding you question, in current architecture and implementation we have
the following point to perform entity persistence customization.
Annotation:
https://docs.jboss.org/hibernate/orm/5.0/javadocs/org/hibernat
Hi all,
I just sent a PR for a minor polishing patch to HCANN which seems
pretty safe and yet scores a solid benefit in terms of performance.
Considering how often we apply changes, I'd volunteer to release a
5.0.1.Final as soon as it's merged, as I assume no more changes will
flow in for a while?
As far as the #7 PR, corry I personally have no idea. The problem is all
the "other" consumers of HCANN I am always told about when I want to change
things in HCANN. I have no idea of the type of impact it might have on
some consumers I know nothing about. For ORM, we do essentially the same
che
Personally I think its a questions of semantics; to me a multi-id load
already implies/indicates a certain loading strategy (Loader). You are
saying you'd like the ability to still decide a specific loading strategy
for multi-id loads. I seriously doubt that is really what you want, but I
do unde
The annotation binder code does this checking. Ultimately (unfortunately)
the binding code does need to understand whether to build a
o.h.mapping.Set, o.h.mapping.List, etc. It makes the reasonable assumption
that the custom collection type (ceylon.collection.MutableSet) at least
implements one o
