Django-pghistory

Latest version: v3.2.0

Safety actively analyzes 630450 Python packages for vulnerabilities to keep your Python projects secure.

Scan your dependencies

Page 4 of 6

2.1.1

Not secure
Trivial

- Format trigger SQL for better compatibility with ``django-pgtrigger``>=4.5 [Wes Kendall, fa04191]

2.1.0

Not secure
Feature

- Add setting to configure JSON encoder for context. [Zac Miller, 430225f]

``django-pghistory`` now uses Django's default JSON encoder
to serialize contexts, which supports datetimes, UUIDs,
and other fields.

You can override the JSON encoder by setting
``PGHISTORY_JSON_ENCODER`` to the path of the class.

Trivial

- Local development enhancements [Wes Kendall, 95a5b1d]

2.0.3

Not secure
Trivial

- Test against Django 4.1 and other CI improvements [Wes Kendall, 953fe1d]

2.0.2

Not secure
Trivial

- Fix ReadTheDocs builds [Wes Kendall, afbc33e]

2.0.1

Not secure
Trivial

- Fix release note rendering and code formatting changes [Wes Kendall, 7043553]

2.0.0

Not secure
Api-Break

- Integration with Django's migration system [Wes Kendall, e0acead]

``django-pghistory`` upgrades ``django-pgtrigger``, which now integrates
with the Django migration system.

Run ``python manage.py makemigrations`` to make migrations for the triggers
created by ``django-pghistory`` in order to upgrade.

If you are tracking changes to third-party models, register the tracker on
a proxy model so that migrations are created in the proper app.

Feature

- Remove dependency on ``django-pgconnection`` [Wes Kendall, aea6056]

``django-pghistory`` no longer requires that users wrap ``settings.DATABASES``
with ``django-pgconnection``.

Page 4 of 6

© 2024 Safety CLI Cybersecurity Inc. All Rights Reserved.