Issue Bug Closed

#14378MySQL 4.1.7 does not tolerate DEFAULT '0' with AUTO_INCREMENT

old_leendert 11/08/04, 17:25 updated 08/12/06, 14:27

Description

With MySQL 4.1.7 (at least, that’s what we’ve tested with), MySQL does not accept “DEFAULT ‘0’” when used with a primary key, thus, tables that have these will not be created. Basically that means that all integer fields that are used as primary key in tables will be generated the wrong way. TYPO3 generates e.g.

uid int(11) auto_increment default ‘0’ not null primary key

The “default ‘0’” is not tolerated by MySQL in this case anymore.

(issue imported from #M472)

Reviews 0

No change resolves or names this issue in its commit message, and no comment links one.