Regarding row-level auditing and field-level auditing

www.digitalocean.com/.../how-to-manage-and-use-mysql-database-triggers-on-ubuntu-18-04

Hi Stefan,

first of all, Thanks for your immediate response.

i am having some knowledge regarding the things that we do with triggers in general.

i need info particularly related to field-level auditing with a sample example

This is not specific to Appian in any way and we do not know what you want to achieve.

In general, my suggestion is to implement a copy-on-write mechanism using a trigger to store a copy of the old data to a separate table before insert. Then you have all versions of the data if needed.

Hi Mohan - I try to consider the big picture here. What is the actual business requirement? Who needs to be able to see the audit data? What should it contain? How long does it need to be kept for? Do they need to see a full "before and after" view of every change? Or only certain changes? Do you need a full history, or just details on who and when the last change was made? There's way more to this than just the one narrow technical option being asked here. 

Thanks for the Reply,

I got the articles related to it, and also I had completed that one.

Let me example you with an example,

 Here, in my case, I have a customer table.

Row-Level Auditing: If the name of the customer is updated, then that entire record should be audited in customer_rowAudit table.

Field-Level Auditing: If the name of customer is updated, then that field should be audited in cutomer_fieldAudit table with previous value, field name, updated value and customer ID.