|
From: Fabio M. (JIRA) <nh...@gm...> - 2011-05-16 15:01:41
|
[ http://216.121.112.228/browse/NH-2615?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Fabio Maulo updated NH-2615:
----------------------------
Issue Type: Bug (was: Improvement)
Related to what we will do with NH-2705, ignoring the "Invalid join", we should allow two possible syntax:
1)s.Query<ItemBase>().Fetch(p => p.SubItem.Details).ToList()
2)s.Query<ItemBase>().Fetch(p => p.SubItem).ThenFetch(p => p.Details).ToList()
1) in practice the same behavior you can already write a HQL
2) if we ignore the "Invalid join" we may allow the concatenation of the property path between Fetch and ThenFetch when the property of Fetch is a component.
between this and the related issue we have 4 or more issues of different type/priority (a nice pot-pourri...btw understandable in this situation).
> Linq Fetch cannot traverse through components
> ---------------------------------------------
>
> Key: NH-2615
> URL: http://216.121.112.228/browse/NH-2615
> Project: NHibernate
> Issue Type: Bug
> Components: Linq Provider
> Affects Versions: 3.0.0.GA
> Reporter: Jerome Haltom
>
> Subject seems to say it all. Gets an exception inside NH saying that the join is incorrect.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://216.121.112.228/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
|