mariadb/mysql-test/suite/vcol
Monty 4cd2a0eb56 MDEV-15243 Crash with virtual fields and row based binary logging
The cause of this was several different bugs:

- When using binary logging with binlog_row_image=FULL
  the all bits in read_set was set, which caused a
  different (wrong) pattern for marking vcol_set.
- TABLE::mark_virtual_columns_for_write() didn't in all
  cases mark vcol_set with the vcol_field.
- TABLE::update_virtual_fields() has to update all
  vcol fields on REPLACE if binary logging with FULL
  is used.
- VCOL_UPDATE_INDEXED should update all vcol fields part
  of an index that was not updated by VCOL_UPDATE_FOR_READ
- max_row_length() calculated length of NULL and not
  used fields. This didn't cause any crash, but used
  more memory than needed.
2018-05-24 18:55:12 +03:00
..
inc Merge branch 'bb-10.2-serg-merge' into 10.2 2017-02-11 09:45:34 +01:00
r MDEV-15243 Crash with virtual fields and row based binary logging 2018-05-24 18:55:12 +03:00
t MDEV-15243 Crash with virtual fields and row based binary logging 2018-05-24 18:55:12 +03:00
disabled.def MDEV-11836 vcol.vcol_keys_myisam fails in buildbot and outside 2017-02-13 18:12:04 +01:00