Bug #2138 | difference InnoDB / MyISAM in create index | ||
---|---|---|---|
Submitted: | 17 Dec 2003 3:08 | Modified: | 17 Dec 2003 8:10 |
Reporter: | Werner Stuerenburg | Email Updates: | |
Status: | Not a Bug | Impact on me: | |
Category: | MySQL Server: InnoDB storage engine | Severity: | S3 (Non-critical) |
Version: | 4.0.15, 4.1.1 | OS: | Windows (Win2K) |
Assigned to: | CPU Architecture: | Any |
[17 Dec 2003 3:08]
Werner Stuerenburg
[17 Dec 2003 6:54]
Dean Ellis
Verified in 4.0.17 (and changing category). This seems an incredibly unlikely thing for someone to want to do. :) May just need to note it in the InnODB Restrictions chapter.
[17 Dec 2003 8:10]
Heikki Tuuri
Werner, InnoDB really does not allow creation of an index where the same column appears twice. This is only documented in a changelog note: " MySQL/InnoDB-3.23.54, December 12, 2002 ... Fixed a bug: if an index contains some column twice, and that column is updated, the table will become corrupt. From now on InnoDB prevents creation of such indexes. " Regards, Heikki
[17 Dec 2003 9:55]
Werner Stuerenburg
Well, yes, I don't think that the bug is with InnoDB; it should be impossible for MyISAM as well, I guess. The behaviour should be identical, right?