4 Commits

Author	SHA1	Message	Date
Sergey Glukhov	7704e3c2c2	Bug#56862 Execution of a query that uses index merge returns a wrong result ... In case of low memory sort buffer QUICK_INDEX_MERGE_SELECT creates temporary file where is stores row ids which meet QUICK_SELECT ranges except of clustered pk range, clustered range is processed separately. In init_read_record we check if temporary file is used and choose appropriate record access method. It does not take into account that temporary file contains partial result in case of QUICK_INDEX_MERGE_SELECT with clustered pk range. The fix is always to use rr_quick if QUICK_INDEX_MERGE_SELECT with clustered pk range is used.	2010-11-23 13:18:47 +03:00
Magne Mahre	f43d6c2b73	Bug #54606 innodb fast alter table + pack_keys=0 prevents ... adding new indexes A fast alter table requires that the existing (old) table and indices are unchanged (i.e only new indices can be added). To verify this, the layout and flags of the old table/indices are compared for equality with the new. The PACK_KEYS option is a no-op in InnoDB, but the flag exists, and is used in the table compare. We need to check this (table) option flag before deciding whether an index should be packed or not. If the table has explicitly set PACK_KEYS to 0, the created indices should not be marked as packed/packable.	2010-09-16 12:51:08 +02:00
Sergey Glukhov	58f1c5fef3	Bug#38999 valgrind warnings for update statement in function compare_record() ... (InnoDB plugin branch)	2010-06-09 16:17:18 +04:00
Marko Mäkelä	72f68480fc	Copy built-in InnoDB tests to mysql-test/suite/innodb_plugin.	2010-06-03 12:48:59 +03:00