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
The current database schema provides all that is needed for a granular data access control. Although, its use requires us to first ideate a future-proof system (query filters to use in where clauses?, query header injection with schema-level RLS?, etc.) and then implement reusable query helpers.
List of actions
Establish an authorization system and its level of implementation
Implement query helpers
Adjust current db schema (ONLY IF REQUIRED)
Apply to authorization system to queries across app
The text was updated successfully, but these errors were encountered:
Chosen approach for now is to provide a module with helper filters (where values) or sub queries (select) that can then be added to existing queries. This enables for a modular building of queries with blocks from different concerns (retrieving translations, authorization, etc.).
RLS is coming soon to drizzle, but for the time being we will only rely on helper query filters and per-request authorization using the permission rules dictionnary.
Task Description
The current database schema provides all that is needed for a granular data access control. Although, its use requires us to first ideate a future-proof system (query filters to use in
where
clauses?, query header injection with schema-level RLS?, etc.) and then implement reusable query helpers.List of actions
The text was updated successfully, but these errors were encountered: