You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If setting `DJANGO_EASY_AUDIT_CHECK_IF_REQUEST_USER_EXISTS` set to `False`, no `request.user` validation is made on DB.
This allow the calling proejct to ignore user validation and speed up audit creation, plus, save some DB queries.
Copy file name to clipboardExpand all lines: README.md
+5-1Lines changed: 5 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -106,7 +106,11 @@ Below are some of the settings you may want to use. These should be defined in y
106
106
determined by the `pre_save` handler sees that there are no changed fields. We are keeping it off by default so that
107
107
projects that wish to use this (potentially less `CRUDEvent`) can choose to turn it on! And those that do not want it (yet or ever),
108
108
or those that do not closely follow the release notes of this project will have one less worry when upgrading.
109
-
109
+
110
+
*`DJANGO_EASY_AUDIT_CHECK_IF_REQUEST_USER_EXISTS`
111
+
112
+
By default this is`True`, but this allows the calling project to make easyaudit ignore user validation on audit event creation.
113
+
This is useful when you have a app with soft delete or no delete on users model. With this set to `False`, easyaudit only fetch `request.user`for audit event creation, no db check is made, meaning you can speed up audit events creation and save some DB calls.
0 commit comments