[Typo3-dev] Important TYPO3 bug (with MySQL 4.1.7)

[Christian Jul Jensen]

"Leendert Brouwer [Netcreators]" <leendert at netcreators.nl> writes:

> We've just noticed that there is a bug in the TYPO3 code that
> generates the SQL dumps. 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.

Please make a bug report at bugs.typo3.org

--
- julle