Re: [hibernate-dev] [hibernate-orm] HHH-7572 - Develop API for load-by-multiple-ids (#1136)

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/hibernate/annotatio... which allows us to specify our own implementation of https://docs.jboss.org/hibernate/orm/5.0/javadocs/org/hibernate/persister.... One of its methods is: Object load(Serializable id, Object optionalObject, LockMode lockMode, SessionImplementor session) throws HibernateException Load an instance of the persistent class. and Object load(Serializable id, Object optionalObject, LockOptions lockOptions, SessionImplementor session) throws HibernateException Load an instance of the persistent class. These two methods allows to specify you own Loader implementation to load Entity by IDS, in mentioned issue this part of contract was ignored by changing call sequence on loading by multiple ids. By Single id; org.hibernate.internal.SessionImpl#get->IdentifierLoadAccessImpl->org.hibernate.internal.SessionImpl.IdentifierLoadAccessImpl#load->org.hibernate.event.spi.LoadEventListener#onLoad->org.hibernate.event.internal.DefaultLoadEventListener#loadFromDatasource->org.hibernate.persister.entity.EntityPersister#load By Multiple id: org.hibernate.internal.SessionImpl#byMultipleIds->org.hibernate.internal.SessionImpl.MultiIdentifierLoadAccessImpl#multiLoad->org.hibernate.loader.entity.DynamicBatchingEntityLoaderBuilder#multiLoad So in new API for multiple load we lose at least 2 possible extension points: onLoadEvent, Persister.load (here we could customize loader - specify our own instead hardcoded one) ID(independent multiple or single). So which one approach is correct and future-proof for Single id or Multiple Ids? 20 нояб. 2015 г. 18:19 пользователь "Steve Ebersole" < notifications(a)github.com&gt; написал: