Added option to not track insert statements. #43
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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.