#110438Raise doctrine/dbal to ~4.4.4 and support the MariaDB 12.3 platform
Description
doctrine/dbal 4.4.4 adds Doctrine\DBAL\Platforms\MariaDB120300Platform for MariaDB 12.3. It does not exist in 4.4.0 through 4.4.3, so the current TYPO3 constraint ~4.4.3 allows an installation that does not have it.
Why TYPO3 needs a counterpart class
doctrine/dbal 4 removed the doctrine event system. TYPO3 therefore no longer adjusts platform behaviour through listeners but by extending each platform class and overriding the methods – column type comment handling and the TYPO3 specific table option handling both live there.
CustomPlatformDriverDecorator maps every doctrine platform onto its TYPO3 subclass and ends in default => $platform. A doctrine platform without a TYPO3 counterpart therefore does not fail, it falls through and runs unextended – the TYPO3 adjustments are silently not applied. That is the failure mode this task prevents for anyone running MariaDB 12.3.
What has to be done
- raise
doctrine/dbalto~4.4.4, so the new platform class is guaranteed to be present. The constraint lives in four files, not only in the rootcomposer.json: also intypo3/sysext/core,typo3/sysext/installandtypo3/sysext/redirects. - add
TYPO3\CMS\Core\Database\Platform\MariaDB120300Platform, adopting the traits and method overrides of the other extended MariaDB platform classes, - register it in
CustomPlatformDriverDecorator.
The tilde constraint is kept deliberately: ~4.4.4 resolves to >=4.4.4 and below 4.5.0, so doctrine stays limited to patch level upgrades. A new minor version can carry platform changes that are incompatible with the TYPO3 platform adaptions and overrides, and those need to be reviewed rather than picked up automatically.
Follow-up changes touching platforms
Later changes of this series remove the table option handling from the platform classes. The new class is part of that set and is aligned with the other eight in the same change, so it never diverges from them.