Create Audit Database & Triggers¶
This walkthrough creates a new audit database. For changes to a target database see Change Management.
Create Database¶
With your application configured with a new entity manager for the audit database and your configuration containing the entities you want to audit, it’s time to create your audit database:
php public/index.php orm:schema-tool:create --object-manager=doctrine.entitymanager.orm_zf_doctrine_audit
This command will create the database for the given object manager. Be sure you specify the same object manager as
the configuration audit_object_manager.
A note about migrations: Currently Doctrine doesn’t have a way to run migrations for two databases. It makes sense to have another set of migrations for the audit database. This repository does not try to solve this problem and leaves the use of migrations up to you.
Run Fixtures¶
The audit database requires data, fixtures, to operate. To populate this data run this command:
php public/index.php data-fixture:import zf-doctrine-audit
The audit database has now been created.
Run Triggers¶
The next step is to run the generated triggers on your target database. This is not done directly on the database through code but instead the trigger code is output by the tool. We will be piping this directly to the target database:
php public/index.php audit:trigger-tool:create
Then pipe this output to the target database such as:
php public/index.php audit:trigger-tool:create | mysql -u user -p123 -h mysql target_database
Any triggers with the same names will be removed. This allows you to re-run the trigger sql.
Drop Triggers¶
There is a tool for removing the triggers and functions created by the trigger-tool:
php public/index.php audit:trigger-tool:drop
Use this only if you need to adjust your audited entities then re-run the :create tool.