-
Notifications
You must be signed in to change notification settings - Fork 2
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add database auditability #196
base: main
Are you sure you want to change the base?
Conversation
ec221f1
to
3ec1c2d
Compare
) | ||
).one() | ||
assert pdc7.paiement_cb | ||
assert len(pdc7.audits) == 1 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Maybe it fails because when listening the "after_update" event in an upsert context, the event is never raised on "conflict do update"?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Maybe we should create a custom event?
d406c9e
to
f01ed5b
Compare
f01ed5b
to
f5d9108
Compare
Current benchmark
Comparison with the latest previous benchmark
|
Current benchmark
Comparison with the latest previous benchmark
|
Purpose
We need to be able to track who changed what when on most of our data for auditability purpose.
Proposal
created_by_id
andupdated_by_id
fields in auditable modelstrack_model_changes
utility that can be triggered upon SQLAlchemy events