From: Andrei A. (JIRA) <nh...@gm...> - 2011-05-14 00:18:45
|
[ http://216.121.112.228/browse/NH-2615?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=21074#action_21074 ] Andrei Alecu commented on NH-2615: ---------------------------------- Can't seem to do .Fetch(p=>p.Component.Entity) either, it says the expression is too complex. With .Fetch(p=>p.Component).ThenFetch(p=>p.Entity), it says that the p.Component join is invalid. I believe the proper solution to this would be to allow a call like: .Fetch(p=>p.Component).ThenFetch(p=>p.Entity) Because otherwise the consumer needs to know specific details about how the mapping is defined, and does not work well in polymorphism situations when several classes inherit the same base but are mapped differently (for example some many use components and some may have many to ones) > 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 |