Skip to content

support doctrine dbal 4 #54039

Open
Open
@dbu

Description

@dbu

Description

For now, the symfony/orm-pack locks doctrine/dbal to version 3 because Symfony relies on the deprecated schema extension events that have been removed in dbal 4.

The events are used in MessengerTransportDoctrineSchemaListener (in the end to add a postgres notifier for symfony/messenger).

Typo3 replaces the platform driver to use custom extended platform implementations that can add to the schema. I do not yet see where exactly we could do that for the notifier - the typo3 changes e.g. in PostgreSQLSchemaManager are to tweak how columns are defined. for the notifier, we need to add completely custom SQL outside of the table definition.

Before i dig deeper, i wanted to ask for input on this, opinions or pointers where this should happen, and where in symfony we should replace the classes.

Notes:

  • MessengerTransportDoctrineSchemaListener (and its test) is the only place in all of symfony/symfony in the 7.1 branch that mentions any DBAL\Event things. fixing this one place will be enough.

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions