summaryrefslogtreecommitdiff
path: root/mysql-test/suite/innodb/t/innodb-32k-crash.test
diff options
context:
space:
mode:
authorMarko Mäkelä <marko.makela@mariadb.com>2017-01-17 17:08:00 +0200
committerMarko Mäkelä <marko.makela@mariadb.com>2017-01-18 08:43:11 +0200
commit085b292a47ee8a6fb141c575e7d8f5ed3b4206bd (patch)
treeb04ef35ebd6934f5a62a4a5396f6428dd4c6acc9 /mysql-test/suite/innodb/t/innodb-32k-crash.test
parent7cf97ed4ee93f7df6d021ad54b9f09964a943c82 (diff)
downloadmariadb-git-085b292a47ee8a6fb141c575e7d8f5ed3b4206bd.tar.gz
MDEV-11824 Allow ROW_FORMAT=DYNAMIC in the InnoDB system tablespace
When MySQL 5.7.9 (and MariaDB Server 10.2) introduced innodb_default_row_format and made ROW_FORMAT=DYNAMIC the default, it became possible to create any ROW_FORMAT tables in the InnoDB system tablespace, except ROW_FORMAT=COMPRESSED. In MySQL 5.7, it is possible to create ROW_FORMAT=DYNAMIC tables when TABLESPACE=innodb_system is explicitly specified. Because MariaDB Server 10.2 does not support the MySQL 5.7 TABLESPACE=innodb_system attribute for tables, we should allow ROW_FORMAT=DYNAMIC when innodb_file_per_table=0. Also, remove the test innodb_zip.innodb-create-options, which was an outdated copy of innodb_zip.create_options.
Diffstat (limited to 'mysql-test/suite/innodb/t/innodb-32k-crash.test')
0 files changed, 0 insertions, 0 deletions