- Ensure installation of pghistory context function is installed across multiple databases [Wes Kendall, d06c758]
2.4.0
Not secure
Bug
- Fix issues related to the ``dumpdata`` command [Wes Kendall, 8cb8036]
Django's ``dumpdata`` command is now compatible with pghistory's AggregateEvent model.
2.3.0
Not secure
Bug
- Check that "pgtrigger" is in settings.INSTALLED_APPS [Wes Kendall, fa86205]
A check is registered with Django's check framework to verify that "pgtrigger" is in settings.INSTALLED_APPS when using ``django-pghistory``.
Docs were also updated to note the requirement of pgtrigger in INSTALLED_APPS. - Install context tracking function in a migration [Wes Kendall, 516dc14]
The Postgres pghistory function is now installed in a migration, alleviating issues that would happen when trying to migrate pghistory triggers.
2.2.2
Not secure
Trivial
- Reference PK of user instead of ID in middleware for DRF-based flows [Wes Kendall, 2193e2b]
2.2.1
Not secure
Trivial
- Do additional safety checks in middleware [Wes Kendall, 9678d83]
Use ``settings.PGHISTORY_MIDDLEWARE_METHODS`` to configure which methods are tracked in the middleware. Defaults to ``("GET", "POST", "PUT", "PATCH", "DELETE")``.