mirror of
https://github.com/jazzband/django-auditlog.git
synced 2026-04-20 15:01:05 +00:00
2a7fc23b29
* Modify ``change`` field to be a json field. Storing the object changes as a json is preferred because it allows SQL queries to access the change values. This work moves the burden of handling json objects from an implementation of python's json library in this package and puts it instead onto the ORM. Ultimately, having the text field store the changes was leaving them less accessible to external systems and code that is written outside the scope of the django auditlog. This change was accomplished by updating the field type on the model and then removing the JSON dumps invocations on write and JSON loads invocations on read. Test were updated to assert equality of dictionaries rather than equality of JSON parsable text. Separately, it was asserted that postgres will make these changes to existing data. Therefore, existing postgres installations should update the type of existing field values without issue. * Add test coverage for messages exceeding char len The "Modify change field to be a json field" commit reduced test coverage on the mixins.py file by 0.03%. The reduction in coverage was the result of reducing the number of operations required to achieve the desired state. An additional test was added to increase previously uncovered code. The net effect is an increase in test case coverage. * Add line to changelog Better markdown formatting Co-authored-by: Hasan Ramezani <hasan.r67@gmail.com> * Update CHANGELOG text format More specific language in the improvement section regarding `LogEntry.change` Co-authored-by: Hasan Ramezani <hasan.r67@gmail.com> * Update migration to show Django version 4.0 Co-authored-by: Hasan Ramezani <hasan.r67@gmail.com> * Update CHANGELOG to show breaking change Running the migration to update the field type of `LogEntry.change` is a breaking change. Co-authored-by: Hasan Ramezani <hasan.r67@gmail.com> * Update serial order of migrations * Adjust manager method for compatibility The create log method on the LogEntry manager required an additional kwarg for a call to create an instance regardless of a change or not. This felt brittle anyway. The reason it had worked prior to these changes was that the `change` kwarg was sending a string "null" and not a None when there were no changes. Co-authored-by: Hasan Ramezani <hasan.r67@gmail.com> |
||
|---|---|---|
| .. | ||
| 0001_initial.py | ||
| 0002_auto_support_long_primary_keys.py | ||
| 0003_logentry_remote_addr.py | ||
| 0004_logentry_detailed_object_repr.py | ||
| 0005_logentry_additional_data_verbose_name.py | ||
| 0006_object_pk_index.py | ||
| 0007_object_pk_type.py | ||
| 0008_action_index.py | ||
| 0009_alter_logentry_additional_data.py | ||
| 0010_alter_logentry_timestamp.py | ||
| 0011_logentry_serialized_data.py | ||
| 0012_add_logentry_action_access.py | ||
| 0013_alter_logentry_timestamp.py | ||
| 0014_logentry_cid.py | ||
| 0015_alter_logentry_changes.py | ||
| __init__.py | ||