6.1 Audit section

In order to audit tables in CYPEX, generic changelog triggers are deployed. They send a copy of your changes to a log table. The visual editor then allows you to track all changes in a table and quickly see what has changed where (diff format).

Inside our history table, data is stored in JSON format. This ensures easy analysis, and guarantees that data is stored in a generic, easy-to-handle format– which is not prone to breaking in case data structures change.

More information about changelog triggers:

Database security is always an essential issue in any database application. Especially when critical data is stored, it might be interesting to know who has changed which data when and how. To track changes made to tables in PostgreSQL you can use a generic changelog trigger. CYPEX writes a generic PL/pgSQL function and uses it to audit tables in the system. PostgreSQL provides good support for stored procedures, so this is ideal.

The point of this is to keep track of all changes made to a table. We want to know which operation has taken place. The next important issue is: When a new row is added it will be visible to the trigger procedure. The same applies to deletion and changes.

To find out more, see our blog about changelog triggers, or check Stack Overflow.