#82128Database migration/analyzer fail on VARCHAR default NULL
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?
Reviews 0
No change resolves or names this issue in its commit message, and no comment links one.