Description
Fernando Mato Mira created an issue — 30th September 2013, 10:55:15:
I have a query where I do 2 joins.
The first join is mapped with AddJoin to a collection in the top level objects, and this works.
The second join is mapped with AddJoin to a field in each member of that collection, but the field is not properly filled (trying to access it results in querying for the leaf object again).
Alexander Zaytsev added a comment — 30th September 2013, 11:00:15:
What is the difference to NH-3538?
Fernando Mato Mira added a comment — 30th September 2013, 11:04:04:
NH-3538 is when you try to make a tree of joins.
This is when you have a linear chain of joins, but one of them maps to a collection per parent object instead of a single field per parent object.
Fernando Mato Mira added a comment — 30th September 2013, 11:06:19:
The collection is filled properly, the children of the collection members are not.
Alexander Zaytsev added a comment — 30th September 2013, 11:09:52:
Ok. Could you provide test cases for both issues?
Alexander Zaytsev added a comment — 30th September 2013, 11:10:36:
Ok
2013/10/1 Fernando Mato Mira (JIRA) jira@nhibernate.jira.com
Fernando Mato Mira added a comment — 30th September 2013, 20:19:12:
Looking at the transformer's source code, the problem does not seem to be there, but in the query handling.
Fernando Mato Mira added a comment — 1st October 2013, 12:48:31:
I tried using {} syntax in the query without success (the Hibernate documentation is very poor in this respect).
Somebody posted a solution for a related {} problem, and I also tried it without success: https://hibernate.atlassian.net/browse/HHH-3003
If instead, I try to use multilevel paths in AddJoin, it results in an exception.
I'm thinking the query handler does not know how to process multilevel joins at all.