You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/Cube.js-Backend/Multitenancy-Setup.md
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -104,8 +104,8 @@ cube(`Products`, {
104
104
### User Context vs queryTransformer
105
105
106
106
[USER_CONTEXT](cube#context-variables-user-context) great for use cases where you want to get explicit control over filtering of underlying data seen by users.
107
-
However for use cases where you want to re-use pre-aggregation tables for different users or even tenants [queryTransformer](@cubejs-backend-server-core#options-reference-query-transformer) is much better choice.
108
-
Together with [contextToDataSourceId](@cubejs-backend-server-core#options-reference-context-to-data-source-id) it allows to define both row level security filtering as well as re-use same pre-aggregation set for each of tenants.
107
+
However for use cases where you want to reuse pre-aggregation tables for different users or even tenants [queryTransformer](@cubejs-backend-server-core#options-reference-query-transformer) is much better choice.
108
+
Together with [contextToDataSourceId](@cubejs-backend-server-core#options-reference-context-to-data-source-id) it allows to define both row level security filtering as well as reuse the same pre-aggregation set for each tenant.
109
109
110
110
## Same DB Instance with per Tenant Row Level Security
0 commit comments