Bug #104621
closed
SchemaColumnDefinitionListener throws a type error while "analyze database" in Maintenance module
100%
Description
Since Version TYPO3 11.5.39 i get an error when i try to Analyze Database in Maintenance module in backend.
When i use the version TYPO3 11.5.33 this error does not appear.
Files
Updated by Garvin Hicking 3 months ago
- Related to Bug #97498: MariaDB + enum field generates endless DB comparison loop due to wrong/twice string escaping of default value added
Updated by Garvin Hicking 3 months ago
- Category changed from Backend API to Database API (Doctrine DBAL)
- Status changed from New to Accepted
- Priority changed from Should have to Must have
- Is Regression set to Yes
Updated by Gerrit Code Review 3 months ago
- Status changed from Accepted to Under Review
Patch set 1 for branch 12.4 of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at https://review.typo3.org/c/Packages/TYPO3.CMS/+/85628
Updated by Gerrit Code Review 3 months ago
Patch set 1 for branch 11.5 of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at https://review.typo3.org/c/Packages/TYPO3.CMS/+/85468
Updated by Gerrit Code Review 3 months ago
Patch set 2 for branch 11.5 of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at https://review.typo3.org/c/Packages/TYPO3.CMS/+/85468
Updated by Gerrit Code Review 3 months ago
Patch set 2 for branch 12.4 of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at https://review.typo3.org/c/Packages/TYPO3.CMS/+/85628
Updated by Gerrit Code Review 3 months ago
Patch set 3 for branch 11.5 of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at https://review.typo3.org/c/Packages/TYPO3.CMS/+/85468
Updated by Garvin Hicking 3 months ago
@!frappant webfactory - Many thanks for reporting this so quickly. It seems to be related to you having a DB table with an ENUM but without a DEFAULT setting, which can trigger this.
Are you able to try out the related patch linked here, and see if it fixes your issue?
Updated by Garvin Hicking 3 months ago
- Status changed from Under Review to Resolved
- % Done changed from 0 to 100
Applied in changeset de6fd229d7ba9328f29ff0ba5e70921d542f57ad.
Updated by !frappant webfactory 3 months ago
Garvin Hicking wrote in #note-8:
@!frappant webfactory - Many thanks for reporting this so quickly. It seems to be related to you having a DB table with an ENUM but without a DEFAULT setting, which can trigger this.
Are you able to try out the related patch linked here, and see if it fixes your issue?
Many Thanks for this fast solution. Yes this works fine for us and you was right with your guess about the ENUM
Kind Regards
Updated by Jörn Wagner 3 months ago
Is there an ETA on when this will be included in an official release? We do have a Composer patch ready for this small fix, but I don't want to integrate it into 10 projects. Probably have to wait until mid-September for 11.5.40?
Updated by Garvin Hicking 3 months ago
Unlike the v12 release plan, there is no fixed plan for v11; it happens based on decisions of the release managers when "enough has gathered" to warrant a patchlevel release.
Sadly that's all I can offer at this point.
Updated by Jörn Wagner about 2 months ago
Alright. Since I wasn't keen on composer-patch-ing multiple projects, I changed the ENUM default in the one column that was affected in our projects. Luckily it was in a base package that all installations use. :-)
Updated by Stefan Bürk about 1 month ago
- Has duplicate Bug #105283: ENUM field detection loop fix introduced type errors with default value `null` added
Updated by 