After having read the documentation on ACS objects (well more or less)
and scanning through the source code for acs_object and for that
matter the source contained in postgres.sql (more or less), it's still
not clear to me whether it's already built into acs_object the
facility to manipulate partial orders (i.e. trees). There seems to be
highly optimized code to modify tree_sortkey, but on the other hand,
there does not exist a simple function like acs_object__set_parent()
or acs_object__add_child() or anthing with a name that would obviously
imply such functionality. Additionally, there's nothing in the
documentation of ACS object that says plainly "supports partial order
relationships," but from what I've heard, that's to be expected since
the documenation is way out of date.
So, what is tree_sortkey used for? What could it be used for? Is one
supposed to use the general relationship support instead? How
optimized would that be? How about using attributes?
Looking for a little -- no scratch that a lot of -- direction here.
-Jeff
