Annamalai Gurusami b76a59f5a6 Bug #14007649 65111: INNODB SOMETIMES FAILS TO UPDATE ROWS INSERTED ... BY A CONCURRENT TRANSACTIO The member function QUICK_RANGE_SELECT::init_ror_merged_scan() performs a table handler clone. Innodb does not provide a clone operation. The ha_innobase::clone() is not there. The handler::clone() does not take care of the ha_innobase->prebuilt->select_lock_type. Because of this what happens is that for one index we do a locking read, and for the other index we were doing a non-locking (consistent) read. The patch introduces ha_innobase::clone() member function. It is implemented similar to ha_myisam::clone(). It calls the base class handler::clone() and then does any additional operation required. I am setting the ha_innobase->prebuilt->select_lock_type correctly. rb://1060 approved by Marko		2012-05-10 10:18:31 +05:30
..
btr0btr.c	Revert revno:3452.71.32 (Bug#12612184 fix).	2011-10-26 12:23:57 +03:00
btr0cur.c	Bug #14007649 65111: INNODB SOMETIMES FAILS TO UPDATE ROWS INSERTED	2012-05-10 10:18:31 +05:30
btr0pcur.c	Fix a compiler warning about possibly uninitiaizlied variable.	2012-03-08 17:10:10 +02:00
btr0sea.c	(partially) Fix Bug#55227 Fix compiler warnings in innodb with gcc 4.6	2010-09-14 11:39:34 +03:00