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

Maybe? - please discuss and support us in the linked issue

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.

###Installing the bundle

Simply run assuming you have installed composer.phar or composer binary:

$ php composer.phar require simplethings/entity-audit-bundle

###Enable the bundle

Finally, enable the bundle in the kernel:

// app/AppKernel.php

public function registerBundles()
{
    $bundles = array(
        //...
        new SimpleThings\EntityAudit\SimpleThingsEntityAuditBundle(),
        //...
    );
    return $bundles;
}

###Configuration

Load extension "simple_things_entity_audit" and specify the audited entities (yes, that ugly for now!)

#####app/config/config.yml

simple_things_entity_audit:
    audited_entities:
        - MyBundle\Entity\MyEntity
        - MyBundle\Entity\MyEntity2

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

#####app/config/config.yml

simple_things_entity_audit:
    global_ignore_properties:
        - createdAt
        - updatedAt

###Creating new tables

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

./app/console doctrine:schema:update --dump-sql 

Notice: EntityAudit currently only works with a DBAL Connection and EntityManager named "default".

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

use Doctrine\ORM\EntityManager;
use Doctrine\Common\EventManager;
use SimpleThings\EntityAudit\AuditConfiguration;
use SimpleThings\EntityAudit\AuditManager;

$auditconfig = new AuditConfiguration();
$auditconfig->setAuditedEntityClasses(array(
    'SimpleThings\EntityAudit\Tests\ArticleAudit',
    'SimpleThings\EntityAudit\Tests\UserAudit'
));

$auditconfig->setGlobalIgnoreProperties(array(
    'createdAt',
    'updatedAt'
));

$evm = new EventManager();
$auditManager = new AuditManager($auditconfig);
$auditManager->registerEvents($evm);

$config = new \Doctrine\ORM\Configuration();
// $config ...
$conn = array();
$em = EntityManager::create($conn, $config, $evm);

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

In Symfony2 the AuditReader is registered as the service "simplethings_entityaudit.reader":

class DefaultController extends Controller
{
    public function indexAction()
    {
        $auditReader = $this->container->get('simplethings_entityaudit.reader');
    }
}

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

$auditReader = $auditManager->createAuditReader($entityManager);

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:

$articleAudit = $auditReader->find(
    'SimpleThings\EntityAudit\Tests\ArticleAudit',
    $id = 1,
    $rev = 10
);

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.

$revisions = $auditReader->findRevisions(
    'SimpleThings\EntityAudit\Tests\ArticleAudit',
    $id = 1
);

A revision has the following API:

class Revision
{
    public function getRev();
    public function getTimestamp();
    public function getUsername();
}

$changedEntities = $auditReader->findEntitiesChangedAtRevision(10);

A changed entity has the API:

class ChangedEntity
{
    public function getClassName();
    public function getId();
    public function getRevisionType();
    public function getEntity();
}

$revision = $auditReader->getCurrentRevision(
    'SimpleThings\EntityAudit\Tests\ArticleAudit',
    $id = 3
);

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

simple_things_entity_audit:
    service:
        username_callable: acme.username_callable

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

$auditConfig = new \SimpleThings\EntityAudit\AuditConfiguration();
$auditConfig->setUsernameCallable(function () {
	$username = //your customer logic
    return username;
});

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

simple_things_entity_audit:
    resource: "@SimpleThingsEntityAuditBundle/Resources/config/routing.yml"
    prefix: /audit

This provides you with a few different routes:

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

• Currently only works with auto-increment databases
• Proper metadata mapping is necessary, allow to disable versioning for fields and associations.

• MySQL / MariaDB
• PostgesSQL
• SQLite

We can only really support the databases if we can test them via Travis.

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 ..