Draft for an event with all information after schema change was perfomed

[beberlei]

/cc @dbu

Related:

• support doctrine dbal 4 symfony/symfony#54039

[dbu]

thank you for looking into this. so the idea would be that e.g. symfony messsenger could listen to this, inspect the changes and fire its own sql statements against the connection if it sees that something was done which it wants to alter?

is this event also useful when doctrine migrations are used rather than database updated on the fly?

with dbal 3, symfony was adding extra sql in https://github.com/symfony/symfony/blob/73f8713e143c64dc5f045dcdee7d5e893cccfcd8/src/Symfony/Bridge/Doctrine/SchemaListener/MessengerTransportDoctrineSchemaListener.php#L76C1-L76C38 (and that sql afaik can not be represented in the doctrine schema models.
that sql got saved to the migration file, which was quite nice to review it.

[beberlei]

Yes, something like:

public function onPostSchemaChanged($event)
{
    if (!$this->hasMessengerTable($event)) {
        $event->getEntityManage()->getConnection()->executeStatement($this->getMessengerTableSql());
    }
}

[dbu]

and how can this be integrated with the doctrine migrations? could the listener also add sql into a migration?

[greg0ire]

Cc @wmouwen

[beberlei]

Just to make it clear, I would greenlight this approach, but I need someone else to take over and finish this:

• getters on the event
• tests
• integrate into dropSchema/getDropSchemaSql
• documentation
• end to end test: Does this really work when executing multiple times