6 commits

Author	SHA1	Message	Date
Sergei Golubchik	ee9afef271	mysql-5.5.28	2012-10-16 13:04:42 +02:00
Sergei Golubchik	9a64d0794c	5.3 merge	2012-08-27 18:13:17 +02:00
Sergei Golubchik	1fd8150a5b	5.1 merge ... increase xtradb verson from 13.0 to 13.01	2012-08-22 16:13:54 +02:00
Sergei Golubchik	37f5632212	merged with XtraDB 1.1.8-26.0	2012-06-15 14:54:23 +02:00
Sergei Golubchik	0522307ed1	mysql-5.5 merge	2012-06-14 20:05:31 +02:00
Annamalai Gurusami	391ea219c2	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