Bug #12873 BTREE index on MEMORY table with multiple NULL values doesn't work properly
| Submitted: | 30 Aug 2005 10:30 | Modified: | 5 Jun 2006 21:43 |
|---|---|---|---|
| Reporter: | jocelyn fournier (Silver Quality Contributor) | Email Updates: | |
| Status: | Closed | Impact on me: | |
| Category: | MySQL Server: Memory storage engine | Severity: | S3 (Non-critical) |
| Version: | 4.1.14/5.0 | OS: | Linux (linux) |
| Assigned to: | Sergey Vojtovich | CPU Architecture: | Any |
[30 Aug 2005 10:30]
jocelyn fournier
[11 May 2006 16:16]
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/6257
[24 May 2006 14:05]
Sergey Vojtovich
Pushed into tree currently marked as 5.0.23.
[2 Jun 2006 10:42]
Sergey Vojtovich
Merged into tree currently tagged as 5.1.12.
[5 Jun 2006 21:43]
Mike Hillyer
Documented in changelog:
<listitem>
<para>
A <literal>B-TREE</literal> index on a
<literal>MEMORY</literal> table erroneously reported duplicate
entry error for multiple <literal>NULL</literal> values. (Bug
#12873)
</para>
</listitem>
Portions of this website are copyright © 2001, 2002 The PHP Group
Page generated in 0.053 sec. using MySQL 8.4.7-u6-cloud
Timestamp references displayed by the system are UTC.
Content reproduced on this site is the property of the
respective copyright holders.
It is not reviewed in advance
by Oracle and does not necessarily represent the opinion of
Oracle or any other party.