From: Jerome H. (JIRA) <nh...@gm...> - 2011-03-31 22:25:47
|
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 |
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 |
From: Andrei A. (JIRA) <nh...@gm...> - 2011-05-14 13:28:44
|
[ http://216.121.112.228/browse/NH-2615?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=21077#action_21077 ] Andrei Alecu commented on NH-2615: ---------------------------------- I have submitted a related issue at NH-2705 that contains a test which demonstrates this here bug as well. I think NH-2615 should also be escalated from trivial to major. > 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 |
From: Fabio M. (JIRA) <nh...@gm...> - 2011-05-16 14:08: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: Improvement (was: Bug) Changed to improv. since the Fetch (with join) on a component does not have sense. > Linq Fetch cannot traverse through components > --------------------------------------------- > > Key: NH-2615 > URL: http://216.121.112.228/browse/NH-2615 > Project: NHibernate > Issue Type: Improvement > 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 |
From: Fabio M. (JIRA) <nh...@gm...> - 2011-05-16 14:38:56
|
[ http://216.121.112.228/browse/NH-2615?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=21087#action_21087 ] Fabio Maulo commented on NH-2615: --------------------------------- The test is available inside NH-2705 test. > Linq Fetch cannot traverse through components > --------------------------------------------- > > Key: NH-2615 > URL: http://216.121.112.228/browse/NH-2615 > Project: NHibernate > Issue Type: Improvement > 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 |
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 |
From: Fabio M. (JIRA) <nh...@gm...> - 2011-05-17 17:30:53
|
[ http://216.121.112.228/browse/NH-2615?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Fabio Maulo reassigned NH-2615: ------------------------------- Assignee: Fabio Maulo > 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 > Assignee: Fabio Maulo > > 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 |
From: Fabio M. (JIRA) <nh...@gm...> - 2011-05-17 17:30:58
|
[ http://216.121.112.228/browse/NH-2615?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Fabio Maulo reassigned NH-2615: ------------------------------- Assignee: Fabio Maulo > 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 > Assignee: Fabio Maulo > > 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 |
From: Fabio M. (JIRA) <nh...@gm...> - 2011-05-17 17:35:54
|
[ http://216.121.112.228/browse/NH-2615?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=21103#action_21103 ] Fabio Maulo commented on NH-2615: --------------------------------- The syntax 1 is locked by Remotion.Linq > 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 > Assignee: Fabio Maulo > > 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 |
From: Fabio M. (JIRA) <nh...@gm...> - 2011-05-17 17:45:53
|
[ http://216.121.112.228/browse/NH-2615?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Fabio Maulo resolved NH-2615. ----------------------------- Resolution: Fixed Fix Version/s: 3.2.0Beta1 > 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 > Assignee: Fabio Maulo > Fix For: 3.2.0Beta1 > > > 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 |