Actions
Bug #82128
closedDatabase migration/analyzer fail on VARCHAR default NULL
Status:
Closed
Priority:
Should have
Assignee:
-
Category:
-
Target version:
-
Start date:
2017-08-17
Due date:
% Done:
0%
Estimated time:
TYPO3 Version:
7
PHP Version:
5.6
Tags:
Complexity:
Is Regression:
Sprint Focus:
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?
Actions