Aleksey Midenkov 97aa07abf5 MDEV-21147 Assertion `marked_for_read()' upon UPDATE on versioned table via view ...

"write set" for replication finally got its correct place
(mark_columns_per_binlog_row_image()). When done generally in
mark_columns_needed_for_update() it affects optimization
algorithm. used_key_is_modified, query_plan.using_io_buffer are
wrongly set and that leads to wrong prepare_for_keyread() which limits
read_set.

2019-12-02 11:48:37 +03:00

..

r

MDEV-21147 Assertion `marked_for_read()' upon UPDATE on versioned table via view

2019-12-02 11:48:37 +03:00

t

MDEV-21147 Assertion `marked_for_read()' upon UPDATE on versioned table via view

2019-12-02 11:48:37 +03:00

common_finish.inc

versioning test suite fixes

2019-10-10 00:20:34 +03:00

common.inc

versioning test suite fixes

2019-10-10 00:20:34 +03:00

common.opt

Tests: versioning suite fix when no test_versioning plugin

2019-07-09 10:01:54 +03:00

disabled.def

MDEV-14820 System versioning is applied incorrectly to CTEs

2018-05-12 10:16:45 +02:00

engines.combinations

MDEV-15458 Segfault in heap_scan() upon UPDATE after ADD SYSTEM VERSIONING

2019-05-17 13:53:22 +02:00

engines.inc

…

innodb.combinations

MDEV-17038 ALTER TABLE CHANGE COLUMN c1 c1 bigint NOT NULL - generates error if table uses SYSTEM VERSIONING

2018-11-01 16:42:06 +02:00

innodb.inc

MDEV-17038 ALTER TABLE CHANGE COLUMN c1 c1 bigint NOT NULL - generates error if table uses SYSTEM VERSIONING

2018-11-01 16:42:06 +02:00

key_type.combinations

versioning test suite fixes

2019-10-10 00:20:34 +03:00

key_type.inc

versioning test suite fixes

2019-10-10 00:20:34 +03:00

wait_system_clock.inc

…