[Mondrian] Roles with lots of Members
remberson at edgedynamics.com
Wed Mar 21 17:59:26 EDT 2007
We think we have a work around. Our permission DB will
generate an access value for each leaf Member, but
we can roll these up the Hierarchy. Thus, we will no
require 100,000 entries in a Role Hierarchy Member Map.
Richard Emberson wrote:
> If one wants to do data-level access control and has, say
> 100,000 or 500,000, Members to a Hierarchy, what
> are the issues.
> All access controlled items are stored in Maps.
> I can see that some of the
> Role methods seem to require iterating over the Members
> currently in the Role. Each Hierarchy Map has a Map of
> Members. This might be both large and slow?
> Hierarchies, which there are only a few, require an Object
> be created for each (the Role.HierarchyAccess Object)
> but there will not be too many of them.
> Each user will have their own Role and there may be
> tens of users.
Quis custodiet ipsos custodes:
This email message is for the sole use of the intended recipient(s) and
may contain confidential information. Any unauthorized review, use,
disclosure or distribution is prohibited. If you are not the intended
recipient, please contact the sender by reply email and destroy all
copies of the original message.
More information about the Mondrian