Skip to main content

This package allows you to track changes to fields in the database, saving the previous and new values ​​in the table.

Project description

SQLAlchemy History

SQLAlchemy History is an extension for SQLAlchemy that provides change tracking and history logging for SQLAlchemy models. It allows developers to easily track changes to their database objects over time, providing a comprehensive history of modifications.

Features

  • Track changes made to SQLAlchemy models.
  • Log historical data for audit purposes.
  • Easily integrate with existing SQLAlchemy applications.

How it works

When you change model fields and add the model to a session, via session.add(model) or session.add_all([model]), the event listener "after_update" you defined is triggered. This listener monitors for changes to field values. If changes have been made, an object containing the field changes (HistoryChanges) will be added to the corresponding table.

Installation

To install SQLAlchemy History, call this command:

pip install sqla-history

or

uv add sqla-history

Usage

Implementation HistoryModel

First, determine the model. You should define the field entity_id. You can also define an FK field with a User ID if you need to track who exactly made changes to the model.

Example:

from sqla_history import BaseHistoryChanges


class Base(DeclarativeBase):
    metadata = meta


class User(Base):
    __tablename__ = "user"

    id: Mapped[UUID] = mapped_column(primary_key=True, default=uuid7)
    ...

...


class HistoryChanges(BaseHistoryChanges, Base):
    __tablename__ = "history_changes"

    user_id: Mapped[UUID | None] = mapped_column(
        ForeignKey("user.id", ondelete="SET NULL")
    )
    entity_id: Mapped[UUID] = mapped_column(index=True)

Creation event listener

In this step you need to create an event listener with "after_update" type.

Example:

from sqlalchemy import Connection, String, event
from sqlalchemy.orm import Mapped, Mapper
from sqla_history import InsertStmtBuilder, WithUserChangeEventHandler

class Note(Base):
    __tablename__ = "note"

    id: Mapped[UUID] = mapped_column(primary_key=True, default=uuid7)
    is_active: Mapped[bool] = mapped_column(default=True)
    name: Mapped[str] = mapped_column(String(255))
    description: Mapped[str] = mapped_column(String(512))


@event.listens_for(Note, "after_update")
def create_note_history(
    mapper: Mapper,
    connection: Connection,
    target: Note,
) -> None:
    stmt_builder = InsertStmtBuilder(history_model=HistoryChanges)
    handler = WithUserChangeEventHandler(
        entity_name="note",
        stmt_builder=stmt_builder,
    )
    handler(mapper=mapper, connection=connection, target=target)

See full example

Important notes

1. define event listeners in the same module as the model 2. don't forget to define the entity_id field

Tested SQLAlchemy Events:

  • "after_update"

Project details


Download files

Download the file for your platform. If you're not sure which to choose, learn more about installing packages.

Source Distribution

sqla_history-0.2.0.tar.gz (6.9 kB view details)

Uploaded Source

Built Distribution

If you're not sure about the file name format, learn more about wheel file names.

sqla_history-0.2.0-py3-none-any.whl (6.9 kB view details)

Uploaded Python 3

File details

Details for the file sqla_history-0.2.0.tar.gz.

File metadata

  • Download URL: sqla_history-0.2.0.tar.gz
  • Upload date:
  • Size: 6.9 kB
  • Tags: Source
  • Uploaded using Trusted Publishing? No
  • Uploaded via: uv/0.5.11

File hashes

Hashes for sqla_history-0.2.0.tar.gz
Algorithm Hash digest
SHA256 ea2e33698da5924111065d26438199a7f21838bb646fb8a38feedd2f595b1ada
MD5 99a5cf9247fb470f1dc1956a398b77fd
BLAKE2b-256 d9ec7935aa30e37393956b54c99e618a2afdbafd303104a1f02885300e678a81

See more details on using hashes here.

File details

Details for the file sqla_history-0.2.0-py3-none-any.whl.

File metadata

File hashes

Hashes for sqla_history-0.2.0-py3-none-any.whl
Algorithm Hash digest
SHA256 b54836215ca941ea3ebcfb42091f26c2271d866a28a0a68d36e5837d3916f262
MD5 79a39c9a3c9191d2b10fb2ddd4ba68a7
BLAKE2b-256 7c3961cbe0005a9618e1f2a6101f9c806a50d6330a8e88deebd088265dc4bb29

See more details on using hashes here.

Supported by

AWS Cloud computing and Security Sponsor Datadog Monitoring Depot Continuous Integration Fastly CDN Google Download Analytics Pingdom Monitoring Sentry Error logging StatusPage Status page