prooph/event-store-doctrine-adapter

Doctrine Adapter for ProophEventStore

v3.3.0 2016-10-12 18:32 UTC

Requires

• php: ~5.5|~7.0
• beberlei/assert: ^2.3
• doctrine/dbal: ^2.5
• prooph/common: ^3.7
• prooph/event-store: ^6.3

Requires (Dev)

• container-interop/container-interop: ^1.1
• fabpot/php-cs-fixer: 1.7.*
• phpunit/phpunit: ^4.8
• sandrokeil/interop-config: ^1.0
• satooshi/php-coveralls: ^1.0
• sebastian/comparator: ^1.2

Suggests

• container-interop/container-interop: For usage of provided factories
• sandrokeil/interop-config: For usage of provided factories

Conflicts

• sandrokeil/interop-config: <1.0

BSD-3-Clause

• Jan Sorgalla
• Alexander Miertsch
• Sascha-Oliver Prolic

README

#CAUTION: The Doctrine adapter is not compatible With prooph/event-store v7. Use the new PDO Event Store instead! Support for the adapter will end at 31 December 2017.

Use Prooph Event Store with Doctrine DBAL.

Database Set Up

The database structure depends on the stream strategies you want to use for your aggregate roots. You can find example SQLs for MySql in the scripts folder and an EventStoreSchema tool which you can use an a doctrine migrations scirpt.

The database schema is only a suggestion. The aggregate_type column has a length of 150 chars. If you have very long class names you should increase this length, otherwise it could lead to errors in your application. This length should be equal with the aggregate_type length in the snapshot table.

Limitations

When using MySQL while enabling oneStreamPerAggregate option, the transaction handling is broken! For more information see: prooph/pdo-event-store#6

Requirements

• PHP >= 5.5
• Doctrine DBAL ^2.4
• Prooph Event Store ^5.0

License

Released under the New BSD License.