mariadb/mysql-test/suite/gcol/r
Sergei Golubchik 062f8eb37d cleanup: key algorithm vs key flags
the information about index algorithm was stored in two
places inconsistently split between both.

BTREE index could have key->algorithm == HA_KEY_ALG_BTREE, if the user
explicitly specified USING BTREE or HA_KEY_ALG_UNDEF, if not.

RTREE index had key->algorithm == HA_KEY_ALG_RTREE
and always had key->flags & HA_SPATIAL

FULLTEXT index had  key->algorithm == HA_KEY_ALG_FULLTEXT
and always had key->flags & HA_FULLTEXT

HASH index had key->algorithm == HA_KEY_ALG_HASH or HA_KEY_ALG_UNDEF

long unique index always had key->algorithm == HA_KEY_ALG_LONG_HASH

In this commit:

All indexes except BTREE and HASH always have key->algorithm
set, HA_SPATIAL and HA_FULLTEXT flags are not used anymore (except
for storage to keep frms backward compatible).

As a side effect ALTER TABLE now detects FULLTEXT index renames correctly
2024-11-05 14:00:47 -08:00
..
federated_gcol.result
gcol_archive.result
gcol_blackhole.result
gcol_blocked_sql_funcs_innodb.result
gcol_blocked_sql_funcs_myisam.result
gcol_bug20746926.result
gcol_bugfixes.result MDEV-19123 Change default charset from latin1 to utf8mb4 2024-07-11 10:21:07 +04:00
gcol_column_def_options_innodb.result MDEV-19123 Change default charset from latin1 to utf8mb4 2024-07-11 10:21:07 +04:00
gcol_column_def_options_myisam.result MDEV-19123 Change default charset from latin1 to utf8mb4 2024-07-11 10:21:07 +04:00
gcol_csv.result
gcol_falcon.result
gcol_handler_innodb.result
gcol_handler_myisam.result
gcol_ins_upd_innodb.result
gcol_ins_upd_myisam.result
gcol_keys_innodb.result MDEV-19123 Change default charset from latin1 to utf8mb4 2024-07-11 10:21:07 +04:00
gcol_keys_myisam.result MDEV-19123 Change default charset from latin1 to utf8mb4 2024-07-11 10:21:07 +04:00
gcol_memory.result
gcol_merge.result
gcol_ndb.result
gcol_non_stored_columns_innodb.result MDEV-19123 Change default charset from latin1 to utf8mb4 2024-07-11 10:21:07 +04:00
gcol_non_stored_columns_myisam.result MDEV-19123 Change default charset from latin1 to utf8mb4 2024-07-11 10:21:07 +04:00
gcol_partition_innodb.result
gcol_partition_myisam.result
gcol_purge.result
gcol_rejected_innodb.result
gcol_rollback.result
gcol_select_innodb.result MDEV-19123 Change default charset from latin1 to utf8mb4 2024-07-11 10:21:07 +04:00
gcol_select_myisam.result MDEV-19123 Change default charset from latin1 to utf8mb4 2024-07-11 10:21:07 +04:00
gcol_supported_sql_funcs_innodb.result MDEV-19123 Change default charset from latin1 to utf8mb4 2024-07-11 10:21:07 +04:00
gcol_supported_sql_funcs_myisam.result MDEV-19123 Change default charset from latin1 to utf8mb4 2024-07-11 10:21:07 +04:00
gcol_trigger_sp_innodb.result
gcol_trigger_sp_myisam.result
gcol_update.result
gcol_view_innodb.result
gcol_view_myisam.result
innodb_partition.result
innodb_prefix_index_check.result
innodb_virtual_basic.result MDEV-19123 Change default charset from latin1 to utf8mb4 2024-07-11 10:21:07 +04:00
innodb_virtual_blob.result
innodb_virtual_debug.result MDEV-19123 Change default charset from latin1 to utf8mb4 2024-07-11 10:21:07 +04:00
innodb_virtual_debug_purge.result MDEV-19123 Change default charset from latin1 to utf8mb4 2024-07-11 10:21:07 +04:00
innodb_virtual_fk.result
innodb_virtual_fk_restart.result
innodb_virtual_index.result cleanup: key algorithm vs key flags 2024-11-05 14:00:47 -08:00
innodb_virtual_purge.result
innodb_virtual_rebuild.result
innodb_virtual_stats.result
innodb_wl8114.result MDEV-19123 Change default charset from latin1 to utf8mb4 2024-07-11 10:21:07 +04:00
main_alter_table.result
main_mysqldump.result
rpl_gcol.result MDEV-19123 Change default charset from latin1 to utf8mb4 2024-07-11 10:21:07 +04:00
virtual_index_drop.result MDEV-19123 Change default charset from latin1 to utf8mb4 2024-07-11 10:21:07 +04:00