prooph/event-store-doctrine-adapter

[Deprecated] Doctrine Adapter for ProophEventStore

event-store-doctrine-adapter's Issues

Throw exception if client wants to begin second transaction

It should not be possible to start a second transaction if adapter is in an active transaction.

event_name to short

I use event_name as name of classname, and run out of event_name length in DB. Do you plan give more than 100 chars?

Adjust adapter to support prooph/event-store 5.0

See prooph/event-store#61

Depends on prooph/event-store#60

Documentation

Could you provide more detailed documentation, about how to configure this?

Update to coveralls ^1.0

and use after_success instead of after_script for it

TableNotFoundException for existing table

Did someone already had an issue with the doctrine adapter + mysql where the event is written to the table but you still get a TableNotFoundException?

Sascha-Oliver Prolic @prolic 16:41
If you use a single stream, you have to create that table before you run the application

Fábio Carneiro @fabiocarneiro 16:41
I did that, the row is inserted.

Sascha-Oliver Prolic @prolic 16:41
Oho

Fábio Carneiro @fabiocarneiro 16:42
the event is being stored, but the app still says "TableNotFoundException"
Oo

Sascha-Oliver Prolic @prolic 16:42
Can you provide a reproducible script?
Than open an issue an we can solve that
Without a test case it's hard.
Or harder
In proophessor-do f.e. i never saw such an issue

Fábio Carneiro @fabiocarneiro 16:44
@prolic Base table or view not found: 1146 Table 'testdatabase.event_stream' doesn't exist
but on the database itself, I not only have the table, but the events are being written properly

Sascha-Oliver Prolic @prolic 16:44
And you're sure it exists?

Fábio Carneiro @fabiocarneiro 16:45
100%

Sascha-Oliver Prolic @prolic 16:45
Can you provide a test script?

Bradley Weston @bweston92 16:45
The 1146 is the error code from MySQL

Fábio Carneiro @fabiocarneiro 16:45
yep, but then its translated to an exception by doctrine DBAL "Connection"

Sascha-Oliver Prolic @prolic 16:45
Please open an issue at the doctrine adapter repo

Fábio Carneiro @fabiocarneiro 16:46
I'll try to investigate it and create a failing testcase

Sascha-Oliver Prolic @prolic 16:46
@basz can you take that over?

Memory problem when replaying large streams

When replaying a large stream it is possible to run out of memory. Even if the DoctrineStreamIterator iterates over the pdo statement so that only one event is stored in a php property at a time, the entire result set is fetched into php process memory (at least when using MySql RDBMS, other systems were not checked). This is caused by buffered query mode which is default for MySql. You can turn of the mode but the drawback is that you can only run one unbuffered query per connection at the same time.

See chat history for more details.

Solution:
Rewrite DoctrineStreamIterator to use pagination internally and fetch 1000 events at once.

DoctrineEventStoreAdapterFactory doesn't implement dimensions()

https://github.com/prooph/event-store-doctrine-adapter/blob/master/src/Container/DoctrineEventStoreAdapterFactory.php

as required by the interop/container package 1.0

Transaction handling

see: prooph/pdo-event-store#6

Force datetime format to include microseconds

Depends on prooph/common#36

Schema files not in sync

Please update schema files. Missing causation_id and causation_name fields.