Is a good idea to use self-referencing hierarchy in CSLA.NET?

Reply

Tiago Freitas Leal replied on Sun, Apr 1 2012 11:09 AM

rated by 0 users

Hi TF Zheng,

CSLA.NET offers no direct support for hierarchical data.

One of the approaches is to use a ReadOnly (root) collection where the ReadOnly child objects have a ParentID property. The hierarchy concept is moved out of business objects to UI. That might not be the best approach since the hierarchy is indeed a business concept.

Reply

TF Zheng replied on Sun, Apr 1 2012 7:45 PM

rated by 0 users

Friend,

Each level of my hierarchical data is an editable list of business object with many properties. At least we have four levels in hierarchy. There are two approaches:

One approach is: Each level of business object maps to a data-table. Then, use "Has relation/Forieign-Key" to establish hierarchical object graph/view.

The another approach is: use self-referenceing table of hierarchy.

My question is: which approach is the best if we we use CSLA.NET together with Entity Framework?

Thanks for any suggestions...

TF Zheng

Reply

TF Zheng replied on Fri, Apr 6 2012 10:19 PM

rated by 0 users

Friend,

Each level of my hierarchical data is an editable list of business object with many properties. At least we have four levels in hierarchy. There are two approaches:

One approach is: Each level of business object maps to a data-table. Then, use "Has relation/Forieign-Key" to establish hierarchical object graph/view.

The another approach is: use self-referenceing table of hierarchy.

My question is: which approach is the best if we we use CSLA.NET together with Entity Framework?

Thanks for any suggestions...

TF Zheng