"NOT NULL" removed from SQL gives error with MySQL 3.23.52
Lines 324ff in class.t3lib_install.php
// Remove NOT NULL statements (they are not needed)
$parts = str_replace(' NOT NULL', '', $parts);
results in an error with MySQL 3.23.52 because two new tables (sys_refindex + sys_preview) in TYPO3 4.0 uses a varchar(32) field as primary key and primary keys in that MySQL version seems to require the "NOT NULL" attribute.
This will surely be a problem when people begin to upgrade sites.
(issue imported from #M2777)
Updated by Robert Lemke about 15 years ago
As I don't have a server with MySQL 3.x running, I can't check it myself. But in theory, even MySQL 3.x should accept a varchar definition without a DEFAULT definition.
See http://dev.mysql.com/doc/refman/4.1/en/data-type-defaults.html for more information.
Updated by Ingmar Schlecht about 15 years ago
A new version of the patch is attached FYI, it is already in CVS.
I have well tested it and I'm pretty sure the way this patch does the trick it is the only feasible way.
Now the NOT NULL statements are not removed anymore, but ignored during comparision.
That means the NOT NULL attribute is only taken into account when fields are initially created but it will be ignored during .sql-file/database comparision later on.
This makes it work for all MySQL versions.
Updated by Karsten Dambekalns about 15 years ago
FYI: DBAL still drops all those NOT NULL statements, and even without they only make sense in this case (if needed for a key), as MySQL will never act as expected when NOT NULL is supplied (otherwise TYPO3 would not work the way it does!).
So the only "real" way to fix this is to drop the declaration except for fields used in primary keys...