From: | stan <stanb(at)panix(dot)com> |
---|---|
To: | pgsql-general(at)lists(dot)postgresql(dot)org |
Subject: | Detecting which columns a query will modify in a function called by a trigger |
Date: | 2020-03-02 18:59:04 |
Message-ID: | 20200302185904.GA6528@panix.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-docs pgsql-general |
I need to implement a fairly fine grained security model. Probably a bit
finer that I can do with the standard ownership functionality.
My thinking on this is to create a table that contains the users, and a
"permission bit" for each function that they may want to do, vis a vi
altering an existing row,or rows, or inserting new rows.
Looks relatively straight forward, if fairly time consuming to do. But I
would need to know which column(s) a given query would add..alter from the
function to implement this via a trigger. looks like I see most of what I
need t do this in the docs, but I can't quite figure out if I can get this
down to what column(s) a given trigger will modify. Is this possible?
--
"They that would give up essential liberty for temporary safety deserve
neither liberty nor safety."
-- Benjamin Franklin
From | Date | Subject | |
---|---|---|---|
Next Message | Adrian Klaver | 2020-03-02 19:02:54 | Re: Detecting which columns a query will modify in a function called by a trigger |
Previous Message | PG Doc comments form | 2020-03-02 15:38:01 | Possible typos in the #12.1.1 examples |
From | Date | Subject | |
---|---|---|---|
Next Message | Adrian Klaver | 2020-03-02 19:02:54 | Re: Detecting which columns a query will modify in a function called by a trigger |
Previous Message | Vik Fearing | 2020-03-02 18:30:22 | Re: Not Null Constraint vs Query Planning |