|
|
|
|
|
by kaladin_1
1555 days ago
|
|
Great article! Although, I would say that this merely shows what is possible with the database level security. It might be useful for an internal db with less complicated permission system. Authorisation Libraries on application level are more scalable and more maintainable than this database level security. Also, just by reading the application code you can tell the expected behaviour... |
|
Plus, I don’t see how “just by reading application code you can tell the expected behavior” doesn’t apply to RLS. Policies are written in a consistent format. USING for visibility, WITH CHECK for altering. I only have to keep an eye for these, and I’ll already get a good summary on what it does, no?