diff options
| author | Marko Mäkelä <marko.makela@mariadb.com> | 2019-02-25 15:35:00 +0200 |
|---|---|---|
| committer | Elena Stepanova <elenst@montyprogram.com> | 2019-02-26 16:50:16 +0200 |
| commit | 043c0471960e42d2d43fb5bed3b9a01a196a6ea3 (patch) | |
| tree | 3b66510dcb39ba623088b38d5fbec37fab19009a /mysys/mf_tempfile.c | |
| parent | 0704e70e96d922b82e3b27741da4b5b3d756e1c2 (diff) | |
| download | mariadb-git-bb-10.4-elenst-no-mdev371.tar.gz | |
MDEV-18719 Assertion (c.prtype ^ o->prtype) & ... failed on ALTER TABLEbb-10.4-elenst-no-mdev371
The prtype & DATA_LONG_TRUE_VARCHAR flag only plays a role when
converting between InnoDB internal format and the MariaDB SQL layer
row format. Ideally this flag would never have been persisted in the
InnoDB data dictionary.
There were bogus assertion failures when an instant ADD, DROP, or
column reordering was combined with a change of extending a VARCHAR
from less than 256 bytes to more than 255 bytes. Such changes are
allowed starting with MDEV-15563 in MariaDB 10.4.3.
dict_table_t::instant_column(), dict_col_t::same_format(): Ignore
the DATA_LONG_TRUE_VARCHAR flag, because it does not affect the
persistent storage format.
Diffstat (limited to 'mysys/mf_tempfile.c')
0 files changed, 0 insertions, 0 deletions