Here is simple diagram with my entities. Here are my simple rules. Level1 has no parent level and my contain one ore more Level2 entities. Level2 entities have one Level1 parent and one or more Level3 enitities. Level3 entities have one Level2 parent entity and collection of one or more Items. So there is many-to-many relationship between Level3 and Items.We cannot use composite pattern here because these classes will be very different and there will be no point where we need one common interface for them. That’s why we have one class per level. Also the number of levels is fixed and there is no plan to expand this hierarchy.
By the way, you can model arbitrary class hierarchies on this model and still use this example (as long as it doesn’t hurt performance and you are really sure what you are doing).
Excercise: having Level1 items collection and knowing Level3 item ID find all Items for specified Level3 item and return string of their titles separated by comma. As you don’t have access to source code of data source you must use IList<Level1> and LINQ.
We will use simple class structure given below and we expect that we already got list of Level1 items from some repository or data context.
public class Level1
{
public int Id { get; set; }
public string Title { get; set; }
public IList<Level2> Level2Items { get; set; }
}
public class Level2
{
public int Id { get; set; }
public string Title { get; set; }
public Level1 Parent { get; set; }
public IList<Level3> Level3Items { get; set; }
}
public class Level3
{
public int Id { get; set; }
public string Title { get; set; }
public Level2 Parent { get; set; }
public IList<Item> Items { get; set; }
}
public class Item
{
public int Id { get; set; }
public string Title { get; set; }
}
public string GetItemsStringForLevel3(IList<Level1> level1Items, int level3Id)
{
var items = from l in level1Items
from l2 in l.Level2Items
from l3 in l2.Level3Items
from p in l3.Items
where l3.Id == level3Id
select p.Title;
return string.Join(", ", items.ToArray());
}
--
Happy Programming
