Bug #10164 | Simple GROUP BY with index gives: ERROR 1032 (HY000): Can't find record in '' | ||
---|---|---|---|
Submitted: | 25 Apr 2005 23:20 | Modified: | 7 Jun 2005 12:39 |
Reporter: | Peter Brodersen (Candidate Quality Contributor) | Email Updates: | |
Status: | Duplicate | Impact on me: | |
Category: | MySQL Server: Optimizer | Severity: | S2 (Serious) |
Version: | 4.1.11 | OS: | Linux (Linux 2.4 debian stable) |
Assigned to: | Assigned Account | CPU Architecture: | Any |
[25 Apr 2005 23:20]
Peter Brodersen
[25 Apr 2005 23:31]
Peter Brodersen
I have uploaded mxtest.tgz (containing mxtest.MYI, mxtest.MYD and mxtest.frm) to ftp.mysql.com, pub/mysql/upload/ (I errorously uploaded domain_mx.tgz as well which I aborted - you can ignore and delete that file) I could upload a mysqldump instead if necessary.
[26 Apr 2005 2:37]
Peter Brodersen
"This error only occurs when a key does not exist for the specified field." should read: "This error only occurs when a key *does* exist for the specified field."
[27 Apr 2005 18:41]
MySQL Verification Team
Verified on Slackware 10.0.
[16 May 2005 22:53]
Bill Nesbitt
Few notes: I can recreate this on RH9 4.1.11-standard-log but it does not happen on RH9 4.1.7-standard-log Another work around is to use IGNORE INDEX (keylist) for the problem index.
[23 May 2005 2:21]
Peter Brodersen
The exact same error also occurs after converting the table from MyISAM to InnoDB.
[30 May 2005 1:23]
Peter Brodersen
This looks like the same issue as of bug #9703 - I guess this bug could be closed?
[7 Jun 2005 12:39]
Timour Katchaounov
This bug seems to be duplicate of BUG#9703 which is already fixed. I just tested with the latest 4.1.13 build and the queries from the bug report work fine.
[6 Oct 2005 4:20]
Rod Bacon
Is this issue still floating around? We have a similar issue on NDB (cluster) tables once they get to a certain size. We are running version 4.1.14.