Bug #104621
closed
SchemaColumnDefinitionListener throws a type error while "analyze database" in Maintenance module
Added by !frappant webfactory 3 months ago.
Updated about 1 month ago.
Category:
Database API (Doctrine DBAL)
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
- Related to Bug #97498: MariaDB + enum field generates endless DB comparison loop due to wrong/twice string escaping of default value added
- 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
- Status changed from Accepted to Under Review
@!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?
- Status changed from Under Review to Resolved
- % Done changed from 0 to 100
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
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?
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.
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. :-)
- Has duplicate Bug #105283: ENUM field detection loop fix introduced type errors with default value `null` added
- Status changed from Resolved to Closed
Also available in: Atom
PDF
Updated by 
Updated by 
Updated by 
Updated by 
Updated by 
Updated by 