I want deep queries. Essentially tasks and their sub-tasks can be infinitely deep. I am trying to avoid the "n-1" issue of loading data of hierarchical items via recursive calls. Half of the issue is loading the entities themselves; the other half is loading various properties from other tables for each of those entities.
I have a Beta of my application completed, but network performance is not so good, so I'm exploring several avenues to optimize this. In this case, I'm trying to learn what is possible and what is not both at the actual SQL level and through an ORM as it relates to hierarchical data retrieval. For my application, an ORM is a wonderful thing. On Jan 18, 1:08 pm, Gunnar Liljas <[email protected]> wrote: > That was a good article and it showed the CTE approach to hierarchical > queries. If you use MSSQL and don't need to add any extra criteria (without > complicating the SQL query), it is a good approach. > > The question is, what do you want to accomplish? Deep queries or only two > levels? > > /G > > 2011/1/18 Eric <[email protected]> > > > I know that my initial example does work past one level. > > I don't know what the underlying SQL looks like. > > > See this link: > > >http://blogs.hibernatingrhinos.com/nhibernate/archive/2008/05/14/how-... > > > -- > > You received this message because you are subscribed to the Google Groups > > "nhusers" group. > > To post to this group, send email to [email protected]. > > To unsubscribe from this group, send email to > > [email protected]<nhusers%[email protected]> > > . > > For more options, visit this group at > >http://groups.google.com/group/nhusers?hl=en. -- You received this message because you are subscribed to the Google Groups "nhusers" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/nhusers?hl=en.
