I think it is fine, may be you can only get just the value of the specific setting instead of creating the entire JpaCompliance object.
On 11 February 2018 at 17:01, Steve Ebersole <st...@hibernate.org> wrote: > I am working on HHH-12282. I was thinking that the best solution would be > to check this setting at the time when Join#setOptional is called. The > reason being to centralize the place that this check needs to be done. I > can do it inside the persister as it consumes the Join, but that leads to > duplicated code. > > But in order to fix in the way I just described, we would have to make > JpaCompliance available earlier in the boot process (currently it is built > as part of SessionFactoryOptions/Builder). > > WDYT? > _______________________________________________ > hibernate-dev mailing list > hibernate-dev@lists.jboss.org > https://lists.jboss.org/mailman/listinfo/hibernate-dev > _______________________________________________ hibernate-dev mailing list hibernate-dev@lists.jboss.org https://lists.jboss.org/mailman/listinfo/hibernate-dev
