[RFC] Make sure that features in the doctrine-bridge are related to the right layer

[stof]

Description

Symfony/doctrine-bridge is actually a bridge against multiple Doctrine projects, not against a single package, which can create issues for projects using some of them if features are not properly layers.

Here are the current target (list might not even be exhaustive):

• doctrine/dbal
• doctrine/persistence
• doctrine/orm

Features targeting integrations with DBAL or Persistence must be careful not to introduce a dependency to the ORM. They must be usable for projects using DBAL only, or for projects using the MongoDB ODM (for Persistence).

Example

No response

[stof]

We have a few existing Messenger middlewares that are implemented the wrong way. The DBAL middlewares are currently implemented as ORM-related features that read the connection from the entity manager.

[nicolas-grekas]

In addition, it might make sense to think twice when merging stuff to the bridge:

• sometimes, it might make sense to add the feature to a lower layer
• sometimes, it might make sense to contribute to the bundle instead

Criteria to help decide could be:

• is this stuff generic enough to fit into eg DBAL directly? Talk to them.
• is this stuff useful for a Laravel integration? if yes, then don't put it in the bundle.

This might apply to code we already merged (eg support for DatePoint could likely be moved to DBAL, provided the Doctrine maintainers agree).