Might be worth considering a change to the underlying nested tree model. Currently updates are expensive but reads are very efficient. We could possibly move the tree model management to a standard parent child relationship, and on intitialisation load the entire tree model as a nested tree table in memory. Then we could use nested tree model query of queries to provide fast reads.
Environment
None
Activity
Show:
Geoff Bowers
August 12, 2011 at 3:27 AM
Dropping this from the ticket database. It's still a long term goal but something that should be discussed in "the cage" section of the WIKI rather than an abstract issue.
Major
Might be worth considering a change to the underlying nested tree model. Currently updates are expensive but reads are very efficient. We could possibly move the tree model management to a standard parent child relationship, and on intitialisation load the entire tree model as a nested tree table in memory. Then we could use nested tree model query of queries to provide fast reads.