Using database triggers to reliably track model history

Discover how database triggers can provide a reliable way to track model history, enforcing business logic and ensuring data integrity, while soft deletes can lead to inconsistencies and should be avoided.

Key takeaways

Database triggers can provide a reliable way to track model history, especially for complex applications.
Soft deletes can lead to inconsistencies and leaks, and should be avoided.
PG History uses database triggers to track changes to models, and provides a default admin integration and event log.
Triggers can be used to enforce business logic, such as checking for balance changes before sending an email.
Soft deleted objects can still be queried and included in the event log.
triggers can be used to track not only inserts and updates, but also deletes.
PG History provides a high level of reliability and allows for customization of the event log.
Soft deletes can be replaced with soft leading models, which provide more functionality and flexibility.
Cascading deletes can be handled using triggers, ensuring that all relevant dependencies are deleted.
PG History can be used to create a true immutable audit log, making it difficult for users to manipulate the history.
The library can be used for complex applications, and provides a simple way to track history.
Triggers can be used to track more than just inserts and updates, but also deletes, and provide a more comprehensive view of the data.
PG History provides a high level of customization and flexibility, making it suitable for a wide range of applications.
The library can be used to track history for multiple models and tables, and provides a single, centralized event log.
Soft deleted objects can be included in the event log, providing a complete view of all changes made to the data.
Triggers can be used to prevent data corruption and ensure the integrity of the data.

Using database triggers to reliably track model history

More talks