Index: openacs-4/packages/acs-core-docs/www/permissions-tediously-explained.adp =================================================================== RCS file: /usr/local/cvsroot/openacs-4/packages/acs-core-docs/www/permissions-tediously-explained.adp,v diff -u -r1.1.2.10 -r1.1.2.11 --- openacs-4/packages/acs-core-docs/www/permissions-tediously-explained.adp 21 Jun 2016 07:44:36 -0000 1.1.2.10 +++ openacs-4/packages/acs-core-docs/www/permissions-tediously-explained.adp 23 Jun 2016 08:32:46 -0000 1.1.2.11 @@ -130,8 +130,8 @@ Context Hierarchy
Suppose objects A, B, ..., and F form the following hierarchy.
Table 11.2. Context -Hierarchy Example
This can be represented in the acs_objects table by the following entries:
Table 11.3. acs_objects -example data
The fact that Joe can also read B, C, ..., and F can be derived by ascertaining that these objects are children of A by traversing the context hierarchy. As it turns out, hierarchical queries are expensive. As Rafael -Schloming put it so aptly, Oracle can't -deal with hierarchies for shit. +Schloming put it so aptly, Oracle +can't deal with hierarchies for shit.
One way to solve this problem is to cache a flattened view of the context tree like so: