property Cube.restrictions : MutableMapping[str, MembershipCondition[LevelIdentifier, ‘IN’, bool | int | float | date | datetime | time | str] | RelationalCondition[LevelIdentifier, ‘EQ’, bool | int | float | date | datetime | time | str] | LogicalCondition[MembershipCondition[LevelIdentifier, ‘IN’, bool | int | float | date | datetime | time | str] | RelationalCondition[LevelIdentifier, ‘EQ’, bool | int | float | date | datetime | time | str], ‘AND’]]
Mapping from role to the corresponding restriction. Restrictions limit the data accessible to users based on their roles.- Restrictions on different hierarchies are intersected.
- Restrictions on the same hierarchy are unioned.
Example
atoti.tables.Tables.restrictions, cube restrictions have no impact on tables:
QuerySession has cubes but no tables so there is nothing to merge cube restrictions with.
However, data cubes have their restrictions merged with the ones from the session’s tables:
See also:
atoti.tables.Tables.restrictions.