Store

In the end, the events have to be saved somewhere. The library is based on doctrine dbal and offers two different store strategies.

Info

You can find out more about stores in the library documentation. This documentation is limited to bundle integration.

Store types

We offer two store strategies that you can choose as you like.

Single Table Store

With the single_table everything is saved in one table.

patchlevel_event_sourcing:
    store:
        type: single_table

Note

You can switch between strategies using the pipeline.

Multi Table Store

With the multi_table a separate table is created for each aggregate type. In addition, a meta table is created by referencing all events in the correct order.

patchlevel_event_sourcing:
    store:
        type: multi_table

Note

You can switch between strategies using the pipeline.

Manage database and schema

The bundle provides you with a few commands with which you can create and delete the database. You can also use it to create, edit and delete the schema.

Create and drop database

bin/console event-sourcing:database:create
bin/console event-sourcing:database:drop

Create, update and drop schema

bin/console event-sourcing:schema:create
bin/console event-sourcing:schema:udapte
bin/console event-sourcing:schema:drop

Use doctrine connection

If you have installed the doctrine bundle, you can also define the connection via doctrine and then use it in the store.

doctrine:
    dbal:
        connections:
            eventstore:
                url: '%env(EVENTSTORE_URL)%'

patchlevel_event_sourcing:
    connection:
        service: doctrine.dbal.eventstore_connection

Warning

If you want to use the same connection as doctrine orm, then you have to set the flag merge_orm_schema. Otherwise you should avoid using the same connection as other tools.

Note

You can find out more about the dbal configuration here.

Migration

You can also manage your schema with doctrine migrations.

In order to be able to use doctrine/migrations, you have to install the associated package.

composer require doctrine/migrations

With this package, further commands are available such as. for creating and executing migrations.

bin/console event-sourcing:migration:diff
bin/console event-sourcing:migration:migrate

You can also change the namespace and the folder in the configuration.

patchlevel_event_sourcing:
    migration:
        namespace: EventSourcingMigrations
        path: "%kernel.project_dir%/migrations"

Merge ORM Schema

You can also merge the schema with doctrine orm. You have to set the following flag for this:

patchlevel_event_sourcing:
    store:
        merge_orm_schema: true

Note

All schema relevant commands are removed if you activate this option. You should use the doctrine commands then.

Warning

If you want to merge the schema, then the same doctrine connection must be used as with the doctrine orm. Otherwise errors may occur!