Hi, I remember that for a bidirectional @OneToOne relationship, the optional = false attribute could instruct Hibernate to always generate a Proxy (because this association cannot be null), so, if the fetch is LAZY, it would not generate a secondary query upon fetching the parent-side entity. I tested it with the latest Hibernate, and when fetching the parent entity it always generates the secondary select for the child entity too. Is this optimization not relevant anymore or is it an issue? Vlad _______________________________________________ hibernate-dev mailing list hibernate-dev(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/hibernate-dev

You just ran into a long standing bug with Hibernate, reported over 5 years ago: https://hibernate.atlassian.net/browse/HHH-3930 Martijn On Fri, Jan 8, 2016 at 4:08 PM, Vlad Mihalcea <mihalcea.vlad(a)gmail.com&gt; wrote: > Hi, > > I remember that for a bidirectional @OneToOne relationship, the optional = > false attribute could instruct Hibernate to always generate a Proxy > (because this association cannot be null), > so, if the fetch is LAZY, it would not generate a secondary query upon > fetching the parent-side entity. > > I tested it with the latest Hibernate, and when fetching the parent entity > it always generates the secondary select for the child entity too. > > Is this optimization not relevant anymore or is it an issue? > > Vlad > _______________________________________________ > hibernate-dev mailing list > hibernate-dev(a)lists.jboss.org > https://lists.jboss.org/mailman/listinfo/hibernate-dev -- Become a Wicket expert, learn from the best: http://wicketinaction.com _______________________________________________ hibernate-dev mailing list hibernate-dev(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/hibernate-dev