summaryrefslogtreecommitdiff
path: root/unittest
diff options
context:
space:
mode:
authorMarko Mäkelä <marko.makela@mariadb.com>2019-05-03 16:47:07 +0300
committerMarko Mäkelä <marko.makela@mariadb.com>2019-05-03 20:02:50 +0300
commitce195987c3c995470992f16ca7a985796d6b65a6 (patch)
treee865c979c084f571c3532b46c7799b43b76942ff /unittest
parent3db94d2403c1f2791bddd43656d7b0d6320b453d (diff)
downloadmariadb-git-ce195987c3c995470992f16ca7a985796d6b65a6.tar.gz
MDEV-19385: Inconsistent definition of dtuple_get_nth_v_field()
The accessor dtuple_get_nth_v_field() was defined differently between debug and release builds in MySQL 5.7.8 in mysql/mysql-server@c47e1751b742454de553937039bbf2bcbe3c6bc7 and a debug assertion to document or enforce the questionable assumption tuple->v_fields == &tuple->fields[tuple->n_fields] was missing. This was apparently no problem until MDEV-11369 introduced instant ADD COLUMN to MariaDB Server 10.3. With that work present, in one test case, trx_undo_report_insert_virtual() could in release builds fetch the wrong value for a virtual column. We replace many of the dtuple_t accessors with const-preserving inline functions, and fix missing or misleadingly applied const qualifiers accordingly.
Diffstat (limited to 'unittest')
0 files changed, 0 insertions, 0 deletions