Bug #60740
closed
DB-migration suggests ALTER TABLE again and again
0%
Description
Example:
ALTER TABLE fe_users CHANGE uid uid int(11) NULL auto_increment;
Current value: int(11) auto_increment
It looks like that's because of the NULL here.
Using TYPO3 6.2.4, MySQL-variant Percona-XtraDB-Cluster-server-55-5.5.37
Updated by Jigal van Hemert over 10 years ago
- Status changed from New to Needs Feedback
In the core the definition of that field is:
uid int(11) unsigned NOT NULL auto_increment
This field is the primary key of the table and as such it cannot allow NULL values. It looks like some extension has added the definition that it would allow NULL values. MySQL/MariaDB will silently convert it into a NOT NULL column to allow the primary key.
The next time the DB migration will find the definition with NULL, compares it to the current situation in the database and suggests again to change it. Ad infinitum.
Updated by Alexander Opitz almost 10 years ago
- Status changed from Needs Feedback to Closed
No feedback within the last 90 days => closing this issue.
If you think that this is the wrong decision or experience this issue again, then please write to the mailing list typo3.teams.bugs with issue number and an explanation or open a new ticket and add a relation to this ticket number.