This has the option to not trigger the audit on inserts. Should be backwards compatible, although I must admit I did not test that as I don't have a setup for doing so.
We have tables that already have the insertion timestamp and we are not too worried about some of the other data tracked in the audits (query/client/etc).
Our use case is tracking changes coming through an ETL pipeline, so there is only one writer, but we don't know what updates we see and how frequently. For that scenario tracking only changes to existing data is more useful, and we'd prefer not going with a fully customized solution.
This has the option to not trigger the audit on inserts. Should be backwards compatible, although I must admit I did not test that as I don't have a setup for doing so.
We have tables that already have the insertion timestamp and we are not too worried about some of the other data tracked in the audits (query/client/etc).
Our use case is tracking changes coming through an ETL pipeline, so there is only one writer, but we don't know what updates we see and how frequently. For that scenario tracking only changes to existing data is more useful, and we'd prefer not going with a fully customized solution.