Search Postgresql Archives

Can row level security policies also be implemented for views?

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



I'm developing an application where strict control of my data is important. Views allow me to build a strict custom reading experience, allowing me to add computed columns and hide private and metadata columns. Row level security allows me strict write control of my data. However, I can't use both technologies together, why?

It seems easy conceptually, RLS just adds a WHERE clause to queries if I'm not mistaken, and conceptually a view is just a query. The CURRENT_USER issue is valid, but personally it's not too big for me as most auth is done through database parameters.

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Index of Archives]     [Postgresql Jobs]     [Postgresql Admin]     [Postgresql Performance]     [Linux Clusters]     [PHP Home]     [PHP on Windows]     [Kernel Newbies]     [PHP Classes]     [PHP Books]     [PHP Databases]     [Postgresql & PHP]     [Yosemite]
  Powered by Linux