Download the PHP package sonata-project/entity-audit-bundle without Composer

EntityAuditBundle

This extension for Doctrine 2 is inspired by Hibernate Envers and allows full versioning of entities and their associations.

Branch	Github Actions	Code Coverage
1.x
2.x.

Support

For general support and questions, please use StackOverflow.

If you think you found a bug or you have a feature idea to propose, feel free to open an issue after looking at the contributing guide.

License

This package is available under the LGPL license.

How does it work?

There are a bunch of different approaches to auditing or versioning of database tables. This extension creates a mirroring table for each audited entitys table that is suffixed with "_audit". Besides all the columns of the audited entity there are two additional fields:

• rev - Contains the global revision number generated from a "revisions" table.
• revtype - Contains one of 'INS', 'UPD' or 'DEL' as an information to which type of database operation caused this revision log entry.

The global revision table contains an id, timestamp, username and change comment field.

With this approach it is possible to version an application with its changes to associations at the particular points in time.

This extension hooks into the SchemaTool generation process so that it will automatically create the necessary DDL statements for your audited entities.

Installation

Installing the bundle

Simply run assuming you have composer:

Enable the bundle

Finally, enable the bundle in the kernel:

Configuration

Load extension "simple_things_entity_audit" and specify the audited entities

If you need to exclude some entity properties from triggering a revision use:

In order to work with other connection or entity manager than "default", use these settings:

If you need to explicitly discard the foreign keys inferred from the audited entities, you can use the disable_foreign_keys parameter:

Creating new tables

Call the command below to see the new tables in the update schema queue.

Installation (Standalone)

For standalone usage you have to pass the entity class names to be audited to the MetadataFactory instance and configure the two event listeners.

Usage

Querying the auditing information is done using a SimpleThings\EntityAudit\AuditReader instance.

In a standalone application you can create the audit reader from the audit manager:

Find entity state at a particular revision

This command also returns the state of the entity at the given revision, even if the last change to that entity was made in a revision before the given one:

Instances created through AuditReader#find() are NOT injected into the EntityManagers UnitOfWork, they need to be merged into the EntityManager if it should be reattached to the persistence context in that old version.

Find Revision History of an audited entity

A revision has the following API:

Find Changed Entities at a specific revision

A changed entity has the API:

Find Current Revision of an audited Entity

Setting the Current Username

Each revision automatically saves the username that changes it. For this to work, the username must be resolved.

In the Symfony web context the username is resolved from the one in the current security context token.

You can override this with your own behaviour by configuring the username_callable service in the bundle configuration. Your custom service must be a callable and should return a string or null.

In a standalone app or Symfony command you can set an username callable to a specific value using the AuditConfiguration.

Viewing auditing

A default Symfony controller is provided that gives basic viewing capabilities of audited data.

To use the controller, import the routing (don't forget to secure the prefix you set so that only appropriate users can get access)

This provides you with a few different routes:

• • Displays a paginated list of revisions, their timestamps and the user who performed the revision
• • Displays the classes that were modified in a specific revision
• • Displays the revisions where the specified entity was modified
• • Displays the data for the specified entity at the specified revision
• • Allows you to compare the changes of an entity between 2 revisions

TODOS

• Currently only works with auto-increment databases
• Proper metadata mapping is necessary, allow to disable versioning for fields and associations.
• It does NOT work with Joined-Table-Inheritance (Single Table Inheritance should work, but not tested)