Issue Task Closed

#106486Adjust `EnumType` and `SetType` type schema handling

Stefan Bürk 04/02/25, 09:24 updated 12/02/25, 14:22

Description

With `doctrine/dbal 4.2.0` the `enum` has been added directly
in DBAL, implementing it slightly different than the original
TYPO3 implementation, which has been mitigated with #105279
and adopted for the `set` type in advance with #105294.

TYPO3 still needs to adopt the options reading existing database
schema provided by a trait to the extended platform classes and
missed to pass the `enum` and `set` option values as `values` to
the `Column` objects instead as `platformOption` key, hidden by
the fact that getting the array representation of a column merges
the platformOptions on the same level with the direct value options.

Upcoming `doctrine/dbal` introduces more phpdoc-block array shapes,
narrowing down possible (allowed) array keys for `platformOptions`
and failing with phpstan in core tests while not beeing a technical
issue.

Reviews 2

History 26

  1. Stefan Bürk commented and changed status Under Review Resolved done 0 % 100 % <span data-processor="relativetime" data-value="2025-04-02T11:10:08+00:00" > 04/02/25, 11:10 </span>

    Applied in changeset commit:79f30d19191854a9bc2e9aa02435048d62209837.