Download the PHP package prolix/entity-audit-bundle without Composer
On this page you can find all versions of the php package prolix/entity-audit-bundle. It is possible to download/install these versions without Composer. Possible dependencies are resolved automatically.
Download prolix/entity-audit-bundle
More information about prolix/entity-audit-bundle
Files in prolix/entity-audit-bundle
Package entity-audit-bundle
Short Description Audit for Doctrine Entities
License LGPL-2.1
Informations about the package entity-audit-bundle
EntityAudit Extension for Doctrine2
Master | 1.0 Branch |
---|---|
documentation | documentation |
WARNING: Master isn't stable yet and it might not be working! Please use version ^1.0
and this documentation: https://github.com/simplethings/EntityAudit/blob/1.0/README.md
This extension for Doctrine 2 is inspired by Hibernate Envers and allows full versioning of entities and their associations.
Is this library still maintained?
Maybe? - please discuss and support us in the linked issue
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 (Standalone)
Installing the lib/bundle
Simply run assuming you have installed composer.phar or composer binary:
For standalone usage you have to pass the EntityManager.
Installation (In Symfony2 Application)
Enable the bundle
Enable the bundle in the kernel:
Configuration
You can configure the audited tables.
app/config/config.yml
Creating new tables
Call the command below to see the new tables in the update schema queue.
Usage
Define auditable entities
You need add Auditable
annotation for the entities which you want to auditable.
You can also ignore fields in an specific entity.
Use AuditReader
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:
In Symfony2 the AuditReader is registered as the service "simplethings_entityaudit.reader":
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 Symfony2 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
.
app/config/config.yml
In a standalone app or Symfony command you can username callable to a specific value using the AuditConfiguration
.
Viewing auditing
A default Symfony2 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)
app/config/routing.yml
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
Supported DB
- MySQL / MariaDB
- PostgesSQL
- SQLite
We can only really support the databases if we can test them via Travis.
Contributing
Please before commiting, run this command ./vendor/bin/php-cs-fixer fix --verbose
to normalize the coding style.
If you already have the fixer locally you can run php-cs-fixer fix .
.