Might be the right tool for you -- very likely so down the road, even if it doesn't have the necessaries to begin with.
Relationships actually mostly are *not* hierarchical in Querki. The most important types are Link Sets and Tag Sets, which are basically arbitrary multi-valued pointers. I'm finding that I tend to use those even in cases where I initially think the data is strictly hierarchical, so that I have more flexibility down the road.
By and large, you rarely set something up with a direct single-valued pointer to a parent. Instead, it's more common for the parent to have a List or Set of its children, or sometimes for the children to have a multi-valued pointer to its "parents".
Where are you picking up on parent-child relationships? Aside from the Model hierarchy itself (which is a strict hierarchy, but that doesn't *mean* as much as it does in most programming languages), its not something I use all the much...
no subject
Relationships actually mostly are *not* hierarchical in Querki. The most important types are Link Sets and Tag Sets, which are basically arbitrary multi-valued pointers. I'm finding that I tend to use those even in cases where I initially think the data is strictly hierarchical, so that I have more flexibility down the road.
By and large, you rarely set something up with a direct single-valued pointer to a parent. Instead, it's more common for the parent to have a List or Set of its children, or sometimes for the children to have a multi-valued pointer to its "parents".
Where are you picking up on parent-child relationships? Aside from the Model hierarchy itself (which is a strict hierarchy, but that doesn't *mean* as much as it does in most programming languages), its not something I use all the much...