Bug #82128
closed
Database migration/analyzer fail on VARCHAR default NULL
0%
Description
In install tool after running "Database analyzer" I get proposed queries like:
ALTER TABLE tablename CHANGE field zzz_deleted_field varchar(255) NOT NULL default NULL;
This is not working as a Not-Null-Field could not setup as default null obviously.
Is this a problem of the created field which was tx_sffeuser_corpcountry here or could it (maybe never the less) handled by SqlSchemaMigrationService to avoid such queries?
Updated by Jakob Berlin over 6 years ago
Obvious workaround if someone run into this:
Run the query on the database directly but modified e.g. to:
ALTER TABLE tablename CHANGE field zzz_deleted_field varchar(255) default NULL;
Updated by Wouter Wolters over 6 years ago
- Status changed from New to Needs Feedback
Is this a problem on version 8.7?
Updated by Riccardo De Contardi over 6 years ago
- Status changed from Needs Feedback to Closed
No feedback since the last 90 days => closing this issue.
Moreover, the whole codebase has changed in this regard (TYPO3 8.7.x uses Doctrine) and we won't change this anymore for version 7.
If you think that this is the wrong decision, please reopen it or open a new issue with a reference to this one. Thank you.