Bug #20357 | Got error 124 from storage engine using MIN and MAX functions in queries | ||
---|---|---|---|
Submitted: | 9 Jun 2006 13:07 | Modified: | 16 May 2007 16:41 |
Reporter: | Shane Bester (Platinum Quality Contributor) | Email Updates: | |
Status: | Closed | Impact on me: | |
Category: | MySQL Server: MyISAM storage engine | Severity: | S2 (Serious) |
Version: | 4.1,5.0,5.1 | OS: | Any (*) |
Assigned to: | Sergey Vojtovich | CPU Architecture: | Any |
[9 Jun 2006 13:07]
Shane Bester
[16 Jun 2006 16:49]
Bugs System
A patch for this bug has been committed. After review, it may be pushed to the relevant source trees for release in the next version. You can access the patch from: http://lists.mysql.com/commits/7771
[26 Jun 2006 10:57]
Sergey Vojtovich
Pushed into trees currently marked as 4.1.21, 5.0.23, 5.1.12.
[26 Jun 2006 14:05]
Jon Stephens
Documented bugfix in 4.1.21/5.0.23/5.1.12 changelogs. Closed.
[16 May 2007 15:47]
MySQL Verification Team
5.0.42 gives error 124 for this testcase: DROP TABLE IF EXISTS `vhg`; CREATE TABLE IF NOT EXISTS `vhg`(`id` TINYINT, KEY `r` (`id`))ENGINE=MyISAM; INSERT INTO `vhg`(`id`) VALUES (1),(2),(3),(4),(5); SELECT `id` FROM `vhg` FORCE INDEX (`r`) WHERE `id`=1; ALTER TABLE `vhg` DISABLE KEYS; SELECT `id` FROM `vhg` FORCE INDEX (`r`) WHERE `id`=1; ALTER TABLE `vhg` ENABLE KEYS; SELECT `id` FROM `vhg` FORCE INDEX (`r`) WHERE `id`=1;
[16 May 2007 16:41]
MySQL Verification Team
moving to a new bug report as this problem is not the same.