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

Stefan Kreisberg stefan at linkfactory.dk
Wed Nov 10 11:46:50 CET 2004


Hehe, two bugs, same issue: anyone come up with a solution?

http://bugs.typo3.org/bug_view_page.php?bug_id=0000416

Mon, 08 Nov 2004 13:07:14 +0100, Leendert Brouwer [Netcreators] 
<leendert at netcreators.nl> skrev:

> 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.
>
>
> Regards,
>
> Leendert Brouwer
> Netcreators





More information about the TYPO3-dev mailing list