`CustomPlatformDriverDecorator` replaces the Doctrine platform
instances with the TYPO3 counterparts, which carry the schema
handling TYPO3 relies on, for example the type aware column comment
handling and the table engine options for `ALTER TABLE`.
The mapping matches on the concrete platform class, so it only
covers platforms a dedicated TYPO3 class exists for. Doctrine adds
platform classes for newer server versions over time, and those were
silently passed through unelevated, losing the TYPO3 behaviour:
* `MariaDB110700Platform` is used from MariaDB 11.7 on. Without
elevation the engine and row format options are missing from the
generated `ALTER TABLE` statements, so such migrations are never
emitted and the schema analyzer keeps offering them.
* `PostgreSQL120Platform` is used from PostgreSQL 12 on. Without
elevation the type aware column comment handling is missing. This
one is latent, as the mapping in `typeRequiresCommentHint()` has
no PostgreSQL entry and the trait is therefore a no-op there.
Both TYPO3 counterparts are added, mirroring their parent classes,
and are registered in the decorator above the class they inherit
from. The MariaDB arms are additionally reordered from the most
specific to the least specific class, so that adding a new one keeps
following an obvious rule.
Testing this requires the extended version matrix from #110240,
without which the affected versions cannot be selected:
> Build/Scripts/runTests.sh -s functional \
-d mariadb -i 11.7 typo3/sysext/core/Tests/Functional/Database
> Build/Scripts/runTests.sh -s functional \
-d mariadb -i 11.8 typo3/sysext/core/Tests/Functional/Database
> Build/Scripts/runTests.sh -s functional \
-d postgres -i 18 typo3/sysext/core/Tests/Functional/Database
Verified with the full `core/Tests/Functional/Database` suite:
MariaDB 11.7 and 11.8 went from 3 errors plus 6 failures and 2
errors plus 6 failures to green. MariaDB 10.4, 10.11 and 11.4, MySQL
8.0 and 8.4 and PostgreSQL 11 and 16 stay green.