django-data-history
A Django application that allows you to store detailed data in the change log and display the detailed information in object's history view.
Install
pip install django-data-history
Usage
INSTALLED_APPS = [
...
"django_middleware_global_request",
"django_middleware_request_id",
"django_static_jquery_ui",
'django_data_history',
...
'django.contrib.admin',
...
]
MIDDLEWARE = [
...
"django_middleware_global_request.middleware.GlobalRequestMiddleware",
"django_middleware_request_id.middlewares.DjangoMiddlewareRequestId",
...
]
SAVE_DATA_HISTORIES_FOR_ALL = True
SAVE_DATA_HISTORIES_FOR = [
"your_app1.model_name1"
]
DO_NOT_SAVE_DATA_HISTORIES_FOR = [
"your_app2.model_name2",
]
Deep usage
How to ignore some fields' values?
Some fields' value are inessential so that we want to ignore their changes.
Simply add django_data_history_excludes in the model.
class TestModel(models.Model):
django_data_history_excludes = ["mod_time"]
mod_time = models.DateTimeField(auto_now=True)
If only mod_time changed, we are not treat the event as a change event, so that we will not make a new record.
How to save data history in separate table?
Simply add DATA_HISTORY_STORAGE_CLASS
property to the model class.
A new DATA_HISTORY_STORAGE_CLASS
must a subclass of django_data_history.models.DataHistoryBase
.
A DATA_HISTORY_STORAGE_CLASS
can be a real class or a absolute-dot-path
to the real class.
Releases
v0.1.0
v0.1.1
- Fix ugettext_lazy problem.
v0.1.2
- Add save_data_histories_for_fk_instance to fix inline edit history missing problem.
v0.1.3
- Fix problems that field name has "+" in fields_map.
v0.1.5
- Using django_middleware_request_id instead of implement request_id inside the app.
v0.1.6
- Fix requirements in setup.py.
v0.1.7
- Fix DataHistoryModelAdmin.get_data_histories function problem.
v0.1.8
- Fix problems in working together with django-import-export.
- Add django_data_history_excludes support.
v0.1.9
- Fix OneToOneField problem.
v0.2.0
- 使用Apache License, Version 2.0开源协议。