Releases: AmbitionEng/django-pghistory
Releases · AmbitionEng/django-pghistory
3.9.1
3.9.0
Changes
- Drop Python 3.9 support, add Python 3.14 support, add Postgres 18 support, add Django 6.0 support by @wesleykendall in #242.
- Don't track transaction-altering statements in context tracking by @valentijnscholten in #239.
3.8.3
Fixes
- Ignore context tracking on VACUUM and other SQL statements that are either irrelevant or cause issues by @wesleykendall in #232.
3.8.2
Fixes
- Fix documentation typos by @valentijnscholten in #229.
3.8.1
Fixes
- Ensure mixed-case table names work with event proxy models by @stephan0h in #226.
3.8.0
Improvements
- Add async support for
pghistory.contextby @qqii in #220. - Add docs for how to migrate existing tracking models to denormalized context by @wesleykendall in #221.
Fixes
3.7.0
Changes
- Ignore appending tracking configuration to
SELECTstatements when tracking context by @stephan0h in #207. - Fix typo in docs by @BStephenBB in #198.
3.6.0
Improvements
-
Add support for statement-level history tracking triggers, offering substantial performance improvements for tracking history over bulk operations by @wesleykendall in #197.
Use
@pghistory.track(level=pghistory.Statement)to leverage statement-level triggers in history tracking. Set is as the default withPGHISTORY_LEVEL = pghistory.Statement.A usage guide was added to the "Performance and Scaling" section of the docs. It notes how it works with conditional history tracking and caveats to be aware of.
-
Optimize context tracking by @wesleykendall in #197.
Context tracking in history triggers is significantly faster when there are many historical events in a span.
Changes
- Add support for Django 5.2, drop support for Postgres 13 by @wesleykendall in #196.