Bug #6784 Strange interaction btw. PRIMARY KEY and FULLTEXT index on REPLACE INTO
Submitted: 23 Nov 2004 22:56 Modified: 24 Nov 2004 22:07
Reporter: Hartmut Holzgraefe Email Updates:
Status: Closed Impact on me:
None 
Category:MySQL Server: MyISAM storage engine Severity:S2 (Serious)
Version:4.1.7 OS:Linux (Linux)
Assigned to: Sergei Golubchik CPU Architecture:Any

[23 Nov 2004 22:56] Hartmut Holzgraefe 
Description:
Using a multiple value list REPLACE INTO with 99+ value lists leads to "duplicate key" errors on a table with a fulltext key. 

How to repeat:
Execute the attached dump.sql and run query q99.sql against it. 
You should see a duplicate key error. Running q99.sql again will
give you the same error with a different key id on each run.
q98.sql is the same as q98.sql but with the last value list removed,
this query runs just fine without errors
[23 Nov 2004 23:03] Hartmut Holzgraefe 
Forgot to mention this: the problem does no longer show when the fulltext index is dropped.
[24 Nov 2004 22:07] Sergei Golubchik 
Thank you for your bug report. This issue has been committed to our
source repository of that product and will be incorporated into the
next release.

If necessary, you can access the source repository and build the latest
available version, including the bugfix, yourself. More information 
about accessing the source trees is available at
    http://www.mysql.com/doc/en/Installing_source_tree.html

Additional info:

fixed in 4.1.8