#18315NOT NULL not recognized correctly on checking database fields
Description
The defail view of an extension in the extension manager tells me that some database updates would be required – for e.g. tt_news I get the following:
ALTER TABLE tt_news CHANGE pid pid int(11) NOT NULL default ‘0’;
Current value: int(11) DEFAULT ’0’
ALTER TABLE tt_news CHANGE tstamp tstamp int(11) unsigned NOT NULL default ‘0’;
Current value: int(11) unsigned DEFAULT ’0’
ALTER TABLE tt_news CHANGE crdate crdate int(11) unsigned NOT NULL default ‘0’;
Current value: int(11) unsigned DEFAULT ’0’
… etc …
The fields are correct in the database but however the check in the extension manager doesn’t recognize the “NOT NULL” correctly.
(issue imported from #M7683)
Reviews 0
No change resolves or names this issue in its commit message, and no comment links one.