| Showing all 6 (Edit, Save, CSV, Feed) |
| ID# | Date | Type | Status | Sev | Version | Target | OS | Summary | Assigned |
|---|---|---|---|---|---|---|---|---|---|
| 41490 | 2008-12-16 8:39 | Server: InnoDB | Verified | S3 | 5.0.x | 6.0-rc | Any | After enlargement of InnoDB page size, the error message become inaccurate. | Marko Mäkelä |
| 38997 | 2008-08-25 8:59 | Server: InnoDB | Verified (134 days) | S3 | 5.0.51, 4.1, 5.0, 5.1, 6.0 bzr | 6.0 | Linux (Stock Debian/SID package) | Multicolumn FKs behave differently than what is suggested in the docs | Calvin Sun |
| 37232 | 2008-06-05 19:38 | Server: InnoDB | Patch approved (112 days) | S3 | 5.1.24 | 6.0-rc | Any | Innodb might get too many read locks for DML with repeatable-read | Inaam Rana |
| 34391 | 2008-02-07 20:27 | Server: InnoDB | In progress (46 days) | S3 | 6.0.5-alpha-debug | 6.0 | Linux (SUSE 10 64-bit) | Character sets: crash if char(), utf32, innodb | Marko Mäkelä |
| 32430 | 2007-11-16 10:35 | Server: InnoDB | Patch pending (18 days) | S3 | 5.1.22, 5.1.23 | 6.0 | Any | 'show innodb status' causes errors Invalid (old?) table or database name in logs | Marko Mäkelä |
| 13942 | 2005-10-12 2:02 | Server: InnoDB | Verified (867 days) | S3 | 5.0.13-rc-nt | 6.0 | Any (WinXP) | automatic FK names > 64 chars long, truncated in information schema | Sunny Bains |
| Showing all 6 (Edit, Save, CSV, Feed) |
