baseapp-django-pghistory 2.8.2

History tracking for Django and Postgres (updated for Baseapp)

This is a fork of https://github.com/Opus10/django-pghistory.

django-pghistory tracks changes to your Django models using Postgres triggers. It offers several advantages over other apps:

• No base models or managers to inherit, no signal handlers, and no custom save methods. All changes are reliably tracked, including bulk methods, with miniscule code.

• Snapshot all changes to your models, create conditional event trackers, or only track the fields you care about.

• Changes are stored in structured event tables that mirror your models. No JSON, and you can easily query events in your application.

• Changes can be grouped together with additional context attached, such as the logged-in user. The middleware can do this automatically.

django-pghistory has a number of ways in which you can configure tracking models for your application’s needs and for performance and scale. An admin integration is included out of the box too.

Quick Start

Decorate your model with pghistory.track. For example:

import pghistory

@pghistory.track(pghistory.Snapshot())
class TrackedModel(models.Model):
    int_field = models.IntegerField()
    text_field = models.TextField()

Above we’ve registered a pghistory.Snapshot event tracker to TrackedModel. This event tracker stores every change in a dynamically-created model that mirrors fields in TrackedModel.

Run python manage.py makemigrations followed by migrate and voila, every change to TrackedModel is now stored. This includes bulk methods and even changes that happen in raw SQL. For example:

from myapp.models import TrackedModel

# Even though we didn't declare TrackedModelEvent, django-pghistory
# creates it for us in our app
from myapp.models import TrackedModelEvent

m = TrackedModel.objects.create(int_field=1, text_field="hello")
m.int_field = 2
m.save()

print(TrackedModelEvent.objects.values("pgh_obj", "int_field"))

> [{'pgh_obj': 1, 'int_field': 1}, {'pgh_obj': 1, 'int_field': 2}]

Above we printed the pgh_obj field, which is a special foreign key to the tracked object. There are a few other special pgh_ fields that we’ll discuss later.

django-pghistory can track a subset of fields and conditionally store events based on specific field transitions. Users can also store free-form context from the application that’s referenced by the event model, all with no additional database queries. See the next steps below on how to dive deeper and configure it for your use case.

Compatibility

django-pghistory is compatible with Python 3.7 - 3.11, Django 3.2 - 4.2, Psycopg 2 - 3 and Postgres 12 - 15.

Documentation

View the django-pghistory docs here to learn more about:

• The basics and terminology.

• Tracking historical events on models.

• Attaching dynamic application context to events.

• Configuring event models.

• Aggregating events across event models.

• The Django admin integration.

• Reverting models to previous versions.

• A guide on performance and scale.

There’s also additional help, FAQ, and troubleshooting guides.

Installation

Install django-pghistory with:

pip3 install django-pghistory

After this, add pghistory and pgtrigger to the INSTALLED_APPS setting of your Django project.

Contributing Guide

For information on setting up django-pghistory for development and contributing changes, view CONTRIBUTING.rst.

Primary Authors

• @wesleykendall (Wes Kendall, [e-mail])

Other Contributors

• @shivananda-sahu

• @asucrews

• @Azurency

• @dracos

• @adamchainz

• @eeriksp