NH-2769 - Linq Fetch over component has no effect on generated SQL

[nhibernate-bot]

cremor created an issue — 16th June 2011, 1:53:04:

NH-2615 fixed the exceptions that occured when a Linq query with a fetch on a component was executed but the fetch has still no effect on the generated SQL.

Attached is a patch that modifies the already existing test (NHSpecificTest\NH2705) so it also checks the generated statement.

---

David Roth added a comment — 10th May 2012, 11:32:17:

Is there any chance for fixing this issue soon? Anyone working on it or planning to do so?
We are using a lot of components in our project and we can`t fetch references with LINQ on collections because of this issue.

---

Oskar Berggren added a comment — 18th January 2013, 8:34:09:

David Roth has made a test case available at:
https://github.com/davrot/nhibernate-core/tree/NH3373

---

David Roth added a comment — 15th February 2013, 13:01:45:

New github location for the testcase: https://github.com/davidroth/nhibernate-core/tree/NH3373

---

ahmed zeyada added a comment — 24th December 2015, 20:57:25:

is there any workaround for this problem ? the only way i can see is fetching it through lazy loading which is not good solution

[hazzik]

Now the generated hql expression is equivalent to

select c from Company c 
join fetch c.Address a
join fetch a.Country 

But it should be:

select c from Company c join fetch c.Address.Country

In other words the Linq translator has to detect that c.Address is mapped as a component and should not add a join fetch for it, but instead for c.Address.Company.

[bahusoid]

@maca88 Isn't this issue already fixed by #1922?

[maca88]

Yes this is fixed and tested by:

nhibernate-core/src/NHibernate.Test/FetchLazyProperties/FetchLazyPropertiesFixture.cs

Line 635 in 848b915

person = s.Query<Person>().Fetch(o => o.Address).ThenFetch(o => o.Continent).FirstOrDefault(o => o.Id == 1);

[davidd4]

Fetch over dynamic component has no effect.
Is this the supposed behavior?
Is there a workaround for it?