mariadb/storage/innobase/handler
Jan Lindström 7b27465e10 MDEV-11974: MariaDB 10.2 encryption does not support spatial indexes
Encryption stores used key_version to
FIL_PAGE_FILE_FLUSH_LSN_OR_KEY_VERSION (offset 26)
field. Spatial indexes store RTREE Split Sequence Number
(FIL_RTREE_SPLIT_SEQ_NUM) in the same field. Both values
can't be stored in same field. Thus, current encryption
implementation does not support encrypting spatial indexes.

fil_space_encrypt(): Do not encrypt page if page type is
FIL_PAGE_RTREE (this is required for background
encryption innodb-encrypt-tables=ON).

create_table_info_t::check_table_options() Do not allow creating
table with ENCRYPTED=YES if table contains spatial index.
2017-02-08 09:05:15 +02:00
..
ha_innodb.cc MDEV-11974: MariaDB 10.2 encryption does not support spatial indexes 2017-02-08 09:05:15 +02:00
ha_innodb.h MDEV-11816 Disallow CREATE TEMPORARY TABLE…ROW_FORMAT=COMPRESSED 2017-01-18 08:42:57 +02:00
ha_innopart.cc MDEV-11816 Disallow CREATE TEMPORARY TABLE…ROW_FORMAT=COMPRESSED 2017-01-18 08:42:57 +02:00
ha_innopart.h MDEV-6076 Persistent AUTO_INCREMENT for InnoDB 2016-12-16 09:19:19 +02:00
handler0alter.cc MDEV-12004 InnoDB wrongly thinks that a column is indexed 2017-02-07 11:55:16 +02:00
handler0alter_innopart.cc Merge InnoDB 5.7 from mysql-5.7.9. 2016-09-02 13:22:28 +03:00
i_s.cc Remove MYSQL_TABLESPACES. 2017-01-18 08:30:43 +02:00
i_s.h MDEV-11785 Remove INFORMATION_SCHEMA.INNODB_TEMP_TABLE_INFO 2017-01-17 12:09:23 +02:00