Bug #18315
closedNOT NULL not recognized correctly on checking database fields
0%
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)
Files
Updated by Oliver Hader over 16 years ago
Caused by rev. 3301 in t3lib_install...
http://code.typo3.org/v4/changeset/3301
Updated by Michael Stucki over 16 years ago
Sorry for this bugger! I changed the case type of all SQL statements including "default '...'" => DEFAULT '...', but it appears like TYPO3 depends on "DEFAULT" being lower-case.
I have reverted this part of the change, and everything runs fine again now.
- michael