V Narayanan 0d61bd9dce Bug#45800 crash when replacing into a merge table and there is a duplicate ... A REPLACE in the MERGE engine is actually a REPLACE into one (FIRST or LAST) of the underlying MyISAM tables. So in effect the server works on the meta data of the MERGE table, while the real insert happens in the MyISAM table. The MERGE table has no index, while MyISAM has a unique index. When a REPLACE into a MERGE table ( and the REPLACE conflicts with a duplicate in a child table) is done, we try to access the duplicate key information for the MERGE table. This information actually does not exist, hence this results in a crash. The problem can be resolved by modifying the MERGE engine to provide us the duplicate key information directly, instead of just returning the MyISAM index number as the error key. Then the SQL layer (or "the server") does not try to access the key_info of the MERGE table, which does not exist. The current patch modifies the MERGE engine to provide the position for a record where a unique key violation occurs. include/myisammrg.h: Bug#45800 crash when replacing into a merge table and there is a duplicate Add a member to the st_mymerge_info structure that will store the duplicate key offset in the MERGE table. This offset will be the sum of the record offset of the MyISAM table within the MERGE table and the offset of the record within the MyISAM table. mysql-test/r/merge.result: Bug#45800 crash when replacing into a merge table and there is a duplicate Result file for the test case. mysql-test/t/merge.test: Bug#45800 crash when replacing into a merge table and there is a duplicate Added test case for both REPLACE and INSERT...ON DUPLICATE UPDATE. storage/myisammrg/ha_myisammrg.cc: Bug#45800 crash when replacing into a merge table and there is a duplicate The info method now will process the HA_STATUS_ERRKEY flag and will return the index and the offset of the duplicate key. storage/myisammrg/ha_myisammrg.h: Bug#45800 crash when replacing into a merge table and there is a duplicate Set the HA_DUPLICATE_POS flag to indicate that the duplicate key information is now available in the MERGE storage engine. storage/myisammrg/myrg_info.c: Bug#45800 crash when replacing into a merge table and there is a duplicate We modify the myrg_status function to return the position of the duplicate key. The duplicate key position in the MERGE table will be the MyISAM file_offset and the offset within the MyISAM table of the start position of the records.		2009-07-30 16:04:41 +05:30
..
archive	Bug #39802 On Windows, 32-bit time_t should be enforced	2009-05-13 15:41:24 +05:30
blackhole
csv
example
federated	Merge from 5.0-bugteam	2009-06-17 16:56:44 +02:00
heap	Bug#35111 - Truncate a MyISAM partitioned table does not reset	2009-07-08 17:41:34 +05:30
ibmdb2i	Bug#45983 ibmdb2i_create_index_option=1 not working for primary key	2009-07-08 14:40:01 +05:30
innobase	merge 5.0-bugteam to 5.1-bugteam	2009-07-24 12:15:06 +05:30
myisam	Merge from 5.0	2009-07-24 21:04:55 +05:00
myisammrg	Bug#45800 crash when replacing into a merge table and there is a duplicate	2009-07-30 16:04:41 +05:30
ndb
Makefile.am