Bug #12695 | Duplicate entry 'xxxxx for key 1 | ||
---|---|---|---|
Submitted: | 20 Aug 2005 15:35 | Modified: | 28 Sep 2005 2:08 |
Reporter: | NULL ! NULL ! | Email Updates: | |
Status: | Closed | Impact on me: | |
Category: | MySQL Server: Optimizer | Severity: | S2 (Serious) |
Version: | 4.1.13 | OS: | Linux (Linux(Redhat9.0)) |
Assigned to: | Sergei Golubchik | CPU Architecture: | Any |
[20 Aug 2005 15:35]
NULL ! NULL !
[8 Sep 2005 11:28]
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/internals/29497
[8 Sep 2005 20:51]
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/internals/29530
[9 Sep 2005 8:55]
Sergei Golubchik
fixed in 4.0.15, 5.0.13.
[9 Sep 2005 22:29]
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/internals/29587
[14 Sep 2005 4:41]
Mike Hillyer
Documented in 4.1.15 and 5.0.13 changelogs: <listitem><para> Performing an <literal>IS NULL</literal> check on the <literal>MIN()</literal> or <literal>MAX()</literal> of an indexed columns produced incorrect results. (Bug #12695) </para></listitem>
[28 Sep 2005 2:08]
Mike Hillyer
Changed: <listitem> <para> Performing an <literal>IS NULL</literal> check on the <literal>MIN()</literal> or <literal>MAX()</literal> of an indexed column in a complex query could produce incorrect results. (Bug #12695) </para> </listitem>