Re: Row level security policy

Thank you for clarifying this. I missed that even though it is there in the second paragraph. - Mark, out and about. > On Nov 14, 2024, at 1:57 AM, Laurenz Albe wrote: > > On Wed, 2024-11-13 at 17:33 -0800, Mark Phillips wrote: >> Given a database table with one policy statement FOR SELECT ap

Re: Row level security policy

On Wed, 2024-11-13 at 17:33 -0800, Mark Phillips wrote: > Given a database table with one policy statement FOR SELECT applied, it is > necessary > to apply additional policy statements for insert, update, and delete > operations? > > My testing indicates that this is case but I haven’t found an

Re: Row level security policy

Well, things did not work as I expected, which means there is more for me to learn. I am new to RLS usage. I want to implement this in a proper manner, so is the behavior described below correct? Are there other aspects of this I need to study? Thanks, in advance. Advice and links to articles a

Re: Row level security policy

Thank you. I will revisit my test cases to be sure I have the use cases covered. - Mark, out and about.On Nov 13, 2024, at 5:36 PM, David G. Johnston wrote:On Wednesday, November 13, 2024, Mark Phillips wrote:Given a database table with one policy statement FOR SELECT app

Re: Row level security policy

On Wednesday, November 13, 2024, Mark Phillips wrote: > Given a database table with one policy statement FOR SELECT applied, it is > necessary to apply additional policy statements for insert, update, and > delete operations? > It isn’t necessary but most conventional use cases would involve est

Re: Row Level Security Policy Name in Error Message

> On 6 Mar 2023, at 01:18, Louis Tian wrote: > Wondering whether there is a way to get the row-level security policy name in > the error message when it's violated. > I am only getting a more generic error message like this. > ERROR: new row violates row-level security policy for table "table_