mariadb/storage/xtradb/row
Marko Mäkelä d361401bc2 Merge 10.1 into 10.2, with some MDEV-14799 fixups
trx_undo_page_report_modify(): For SPATIAL INDEX, keep logging
updated off-page columns twice, so that
the minimum bounding rectangle (MBR) will be logged.
Avoiding the redundant logging would require larger changes
to the undo log format.

row_build_index_entry_low(): Handle SPATIAL_UNKNOWN more robustly,
by refusing to purge the record from the spatial index.
We can get this code when processing old undo log from 10.2.10 or
10.2.11 (the releases affected by MDEV-14799, which was a regression
from MDEV-14051).
2018-01-03 11:56:24 +02:00
..
row0ext.cc move to storage/xtradb 2015-05-04 19:15:28 +02:00
row0ftsort.cc MDEV-12634: Uninitialised ROW_MERGE_RESERVE_SIZE bytes written to tem… 2017-09-14 09:23:20 +03:00
row0import.cc Merge 10.1 into 10.2 2017-11-07 23:02:39 +02:00
row0ins.cc MDEV-9663: InnoDB assertion failure: *cursor->index->name == TEMP_INDEX_PREFIX 2017-11-16 14:05:49 +02:00
row0log.cc Merge 10.0 into 10.1 2017-12-21 17:25:51 +02:00
row0merge.cc Merge branch '10.1' into 10.2 2017-10-24 14:53:18 +02:00
row0mysql.cc Merge 10.0 into 10.1 2017-12-18 20:05:50 +02:00
row0purge.cc Merge 10.0 into 10.1 2018-01-02 21:57:22 +02:00
row0quiesce.cc MDEV-13328 ALTER TABLE…DISCARD TABLESPACE takes a lot of time 2017-11-06 18:08:33 +02:00
row0row.cc 5.6.31-77.0 2016-08-10 19:24:58 +02:00
row0sel.cc Merge 10.0 into 10.1 2017-10-26 13:36:38 +03:00
row0uins.cc Merge 10.0 into 10.1 2017-08-28 15:05:46 +03:00
row0umod.cc Merge 10.0 into 10.1 2017-10-26 13:36:38 +03:00
row0undo.cc Merge 10.0 into 10.1 2017-12-13 19:12:16 +02:00
row0upd.cc MW-402 cascading FK issues 2017-11-08 14:15:41 +02:00
row0vers.cc move to storage/xtradb 2015-05-04 19:15:28 +02:00