This will work, you can just drill down in the linq query public IQueryable GetJobsCategories(IQueryable blogPosts) { return from bp in blogPosts from tag in bp. BlogPostTags select tag; } If you declare the method as such: public static IQueryable GetJobsCategories(this IQueryable blogPosts) You can use it as extension method on queryables. For instance myContext.BlogPosts.
GetJobsCategories().
Yep, simple. I knew I was missing the obvious! Thanks.
– Charlino Dec 18 '09 at 0:58.
I am able to eager load the Parent, Child1 and Grandchild1 data resulting in one query to SQL Server. I need to load the sibling data as well. One approach I have tried is splitting the query into two LINQ to SQL queries and merging the result sets together (not pretty), however upon accessing the sibling data it is lazy loaded anyway.
I've also written LINQ to SQL queries to join in all of the data in hopes that it would eager load the data, however when the LINQ to SQL EntitySet of Child2 or Grandchild1 are accessed it lazy loads the data. The reason for returning the IList is to hydrate business objects. Approaching this problem the wrong way.
I cant really gove you an answer,but what I can give you is a way to a solution, that is you have to find the anglde that you relate to or peaks your interest. A good paper is one that people get drawn into because it reaches them ln some way.As for me WW11 to me, I think of the holocaust and the effect it had on the survivors, their families and those who stood by and did nothing until it was too late.