2023-10-27 - Row Level Security¶
Release¶
Status: Available
Type: DataOps
Date: 2023-10-27
Problem¶
Policy names were based on the column the policy applied to. This did not scale, because a column can have more than one policy.
Solution¶
Give every policy its own unique identifier and use it as the policy name.
Leverage the Magic¶
A small backend change sets the unique identifier whenever a table policy is created or updated.
Last Refreshed¶
Doc Refreshed: 2026-10-25