Hi AntarisZX,
Have you considered using SQL Server HierarchyID to store your tree data? EF doesn't yet support HierarchyID, but it is something that a lot of people are interested in and is something that either the team at Microsoft and/or the community may work on post-EF6.
With regard to your specific pattern, I'm not sure that there would be enough general interest for the team at Microsoft to work on this. However, we would potentially accept a contribution for it. It's worth keeping in mind that it would quite a complicated change to get EF to support this since it would likely require changes to many areas of the stack in order to support view generation, queries, materialization, updates, etc.
Thanks,
Arthur
Have you considered using SQL Server HierarchyID to store your tree data? EF doesn't yet support HierarchyID, but it is something that a lot of people are interested in and is something that either the team at Microsoft and/or the community may work on post-EF6.
With regard to your specific pattern, I'm not sure that there would be enough general interest for the team at Microsoft to work on this. However, we would potentially accept a contribution for it. It's worth keeping in mind that it would quite a complicated change to get EF to support this since it would likely require changes to many areas of the stack in order to support view generation, queries, materialization, updates, etc.
Thanks,
Arthur