Hierarchical Data Storage
Bart Pietercil
bart.pietercil at gmail.com
Sat Feb 10 13:02:10 CST 2007
Hi List,
as I'm new to the features of Valentina, I post this question to
ascertain that I'm on the right track.
The subject says it all: are there in the feature set of Valentina
things I should now when storing hierarchical data?
The model is a company with loosely defined departments (cells in our
db). The cells are just groups of people, but that's not really
relevant for the discussion.
What I would go for in a relational model is described here:
http://www.sitepoint.com/article/hierarchical-data-database/2
However the model described in aforementioned page(the modified
preorder tree traversal storage method) to me has very high
resemblance with the network-model database described in Valentina's
documentation ( intro to the databasemodel)
Further down is noted that the Link abstraction model (re) introduces
the network model for Valentina.
Now I don't really see if working with links would bring an advantage
to the modified preorder tree traversal storage method, but I might
be overlooking something.
The goal must be : one query to obtain all ascendant ID's, one query
to obtain all descendants ID's. ( A manager of a cell is also manager
of the subordinate cell's personnel. So when he says show me all
(from all cells) my personnel status, I want to be able to obtain all
cell id's with one query (not using recursion), at least until
someone comes up with a better way that is :-)
Your comments would be highly appreciated
TIA
Bart Pietercil
More information about the Valentina
mailing list