Fix: Replace deprecated double(11,2) with decimal(10,2) in ext_tables.sql #710
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The ext_tables.sql file used the deprecated MySQL syntax
double(11,2)for decimal fields, which causes constant schema migration prompts when running DB compare.MySQL/MariaDB interprets
double(11,2)ambiguously, and Doctrine DBAL schema comparison detected a type mismatch between the defined schema and what TYPO3 generates from TCA configuration. The TCA defines these fields astype => 'number'withformat => 'decimal', which TYPO3's DefaultTcaSchema class converts to decimal(10,2).This change replaces all occurrences of
double(11,2)withdecimal(10,2)to align with TYPO3's schema generation and eliminate the persistent migration warnings.Affected fields:
Resolves: #711