BUG #15573: Need more clarification in Json

classic Classic list List threaded Threaded
2 messages Options
Reply | Threaded
Open this post in threaded view
|

BUG #15573: Need more clarification in Json

PG Doc comments form
The following bug has been logged on the website:

Bug reference:      15573
Logged by:          selva kumaran
Email address:      [hidden email]
PostgreSQL version: 10.5
Operating system:   Windows 10
Description:        

I have written the below trigger function used for recording changes to
tables into an audit log table.It will record the old and new records, the
table affected, the user who made the change, and a timestamp for each
change in JSON format.

Right now the issue is my business user needs only the particular column
which have changed from old to new not the whole json record.
i.e i need a select query to find the difference between two json columns(
v_old_data and v_new_data ).

Please give me the solution.






CREATE OR REPLACE FUNCTION audit.if_modified_func() RETURNS TRIGGER AS
$body$
DECLARE
    v_old_data json;
    v_new_data json;
BEGIN
    /*  If this actually for real auditing (where you need to log EVERY
action),
        then you would need to use something like dblink or plperl that
could log outside the transaction,
        regardless of whether the transaction committed or rolled back.
    */
 
    /* This dance with casting the NEW and OLD values to a ROW is not
necessary in pg 9.0+ */
 
    IF (TG_OP = 'UPDATE') THEN
        v_old_data := ROW_TO_JSON(OLD.*);
        v_new_data := ROW_TO_JSON(NEW.*);
        INSERT INTO audit.logged_actions
(schema_name,table_name,user_name,action,original_data,new_data,query)
        VALUES
(TG_TABLE_SCHEMA::TEXT,TG_TABLE_NAME::TEXT,session_user::TEXT,substring(TG_OP,1,1),v_old_data,v_new_data);
        RETURN NEW;
    ELSIF (TG_OP = 'DELETE') THEN
        v_old_data := ROW_TO_JSON(OLD.*);
        INSERT INTO audit.logged_actions
(schema_name,table_name,user_name,action,original_data,query)
        VALUES
(TG_TABLE_SCHEMA::TEXT,TG_TABLE_NAME::TEXT,session_user::TEXT,substring(TG_OP,1,1),v_old_data);
        RETURN OLD;
    ELSIF (TG_OP = 'INSERT') THEN
        v_new_data := ROW_TO_JSON(NEW.*);
        INSERT INTO audit.logged_actions
(schema_name,table_name,user_name,action,new_data,query)
        VALUES
(TG_TABLE_SCHEMA::TEXT,TG_TABLE_NAME::TEXT,session_user::TEXT,substring(TG_OP,1,1),v_new_data);
        RETURN NEW;
    ELSE
        RAISE WARNING '[AUDIT.IF_MODIFIED_FUNC] - Other action occurred: %,
at %',TG_OP,now();
        RETURN NULL;
    END IF;
 
EXCEPTION
    WHEN data_exception THEN
        RAISE WARNING '[AUDIT.IF_MODIFIED_FUNC] - UDF ERROR [DATA EXCEPTION]
- SQLSTATE: %, SQLERRM: %',SQLSTATE,SQLERRM;
        RETURN NULL;
    WHEN unique_violation THEN
        RAISE WARNING '[AUDIT.IF_MODIFIED_FUNC] - UDF ERROR [UNIQUE] -
SQLSTATE: %, SQLERRM: %',SQLSTATE,SQLERRM;
        RETURN NULL;
    WHEN OTHERS THEN
        RAISE WARNING '[AUDIT.IF_MODIFIED_FUNC] - UDF ERROR [OTHER] -
SQLSTATE: %, SQLERRM: %',SQLSTATE,SQLERRM;
        RETURN NULL;
END;
$body$
LANGUAGE plpgsql


 CREATE TRIGGER t_if_modified_trg
 AFTER INSERT OR UPDATE OR DELETE ON temp_tbl
 FOR EACH ROW EXECUTE PROCEDURE audit.if_modified_func();

Reply | Threaded
Open this post in threaded view
|

Re: BUG #15573: Need more clarification in Json

David G Johnston
On Thursday, January 3, 2019, PG Bug reporting form <[hidden email]> wrote:

Bug reference:      15573
Logged by:          selva kumaran

 
Please don’t use the bug reporting list for basic user questions.

Right now the issue is my business user needs only the particular column
which have changed from old to new not the whole json record.
i.e i need a select query to find the difference between two json columns(
v_old_data and v_new_data ).

Apply json_each_text to both values, full join on the keys, and filter out pairs with matching values?

David J.