I would like to add to the post above (see stackoverflow for actual query).
It was suggested to me that fetch join (an explicit eager fetch) should only be used for eagerly loading associations, and nothing else. If you need to filter on the eager fetch, you should do a non-eager join (to the same entity) and use that one for filtering and order by. In practice though, I was able to filter on eagerly joined collections w/ out any problems. I don't see how that would impose problems on HQL to SQL generation in hibernate. Any comments could be appreciated. lk On Wednesday, August 31, 2016 at 1:34:21 PM UTC-4, Luke Kurach wrote: > > All, > > Using version Nhibernate 3.3.3 GA. > > The HQL I have created is not correctly translated to SQL. Specifically, > one of the left joins (between plan: Job_Plans table and division: > Code_Plan_Division_Types table) ends up as an inner join in the where > clause. > > > The issue is described at stackoverflow in more detail: > > > > http://stackoverflow.com/questions/39253943/nhibernate-hql-bug-left-join-in-the-wrong-place > > > Regards, > > > lk > -- You received this message because you are subscribed to the Google Groups "nhusers" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/nhusers. For more options, visit https://groups.google.com/d/optout.
