mariadb/storage/innobase/handler
Thirunarayanan Balathandayuthapani 6b63e4ad4a Bug #23219499 CONCURRENT UPDATE DOESN'T APPLY IN VIRTUAL INDEX DURING TABLE REBUILD
Problem:
=======
Concurrent update dml statement doesn't reflect in virtual index during
inplace table rebuild. It results mismatch value in virutal index and
clustered index. Deleting the table content tries to search the mismatch
value in virtual index but it can't find the value. During log update
apply phase, virtual information is being ignored while constructing
the new entry.

Solution:
=========
In row_log_update_apply phase, build the entry with virtual column
information. So that it can reflect in newly constructed virtual index.

Reviewed-by: Jimmy Yang<jimmy.yang@oracle.com>
RB: 14974
2017-04-26 23:03:31 +03:00
..
ha_innodb.cc BUG#25126722 FOREIGN KEY CONSTRAINT NAME IS NULL IN INFORMATION_SCHEMA AFTER RESTART 2017-04-26 23:03:30 +03:00
ha_innodb.h Merge branch '10.1' into 10.2 2017-03-30 12:48:42 +02:00
ha_innopart.cc Bug#21153166: REMOVE UNUSED VARIABLES AND CONVERT GLOBAL SYMBOLS TO STATIC 2017-03-17 12:49:20 +02:00
ha_innopart.h MDEV-6076 Persistent AUTO_INCREMENT for InnoDB 2016-12-16 09:19:19 +02:00
handler0alter.cc Bug #23219499 CONCURRENT UPDATE DOESN'T APPLY IN VIRTUAL INDEX DURING TABLE REBUILD 2017-04-26 23:03:31 +03:00
handler0alter_innopart.cc Merge InnoDB 5.7 from mysql-5.7.9. 2016-09-02 13:22:28 +03:00
i_s.cc Bug#24346574 PAGE CLEANER THREAD, ASSERT BLOCK->N_POINTERS == 0 2017-04-26 23:03:27 +03:00
i_s.h MDEV-11785 Remove INFORMATION_SCHEMA.INNODB_TEMP_TABLE_INFO 2017-01-17 12:09:23 +02:00