mirror of
https://github.com/MariaDB/server.git
synced 2025-01-31 02:51:44 +01:00
88edb1b3ed
When MariaDB 10.1.0 introduced table options for encryption and compression, it unnecessarily changed ha_innobase::check_if_supported_inplace_alter() so that ALGORITHM=COPY is forced when these parameters differ. A better solution is to move the check to innobase_need_rebuild(). In that way, the ALGORITHM=INPLACE interface (yes, the syntax is very misleading) can be used for rebuilding the table much more efficiently, with merge sort, with no undo logging, and allowing concurrent DML operations.
18 lines
524 B
PHP
18 lines
524 B
PHP
-- source include/have_xtradb.inc
|
|
-- source filekeys_plugin.inc
|
|
|
|
create table t1(c1 bigint not null, b char(200)) engine=innodb encrypted=yes encryption_key_id=1;
|
|
show create table t1;
|
|
insert t1 values (12345, repeat('1234567890', 20));
|
|
|
|
alter table t1 encryption_key_id=2;
|
|
show create table t1;
|
|
--error ER_ILLEGAL_HA_CREATE_OPTION
|
|
alter table t1 encryption_key_id=3;
|
|
show create table t1;
|
|
alter table t1 encryption_key_id=33;
|
|
show create table t1;
|
|
alter table t1 encryption_key_id=4;
|
|
show create table t1;
|
|
|
|
drop table t1;
|