Bug #14378
MySQL 4.1.7 does not tolerate DEFAULT '0' with AUTO_INCREMENT
| Status: | Closed | Start date: | 2004-11-08 | |
|---|---|---|---|---|
| Priority: | Should have | Due date: | ||
| Assigned To: | Ingmar Schlecht | % Done: | 0% |
|
| Category: | Backend API | Spent time: | - | |
| Target version: | - | |||
| TYPO3 Version: | 3.7.0 | Is Regression: | ||
| PHP Version: | Sprint Focus: | |||
| Complexity: |
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)
Related issues
History
#1 Updated by Ingmar Schlecht over 10 years ago
This is a dupe of #0000416.