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
..
CMakeLists.txt	Update FSF Address	2019-05-11 21:29:06 +03:00
ha_tina.cc	Merge 11.4 into 11.6	2024-10-03 16:09:56 +03:00
ha_tina.h	cleanup: key algorithm vs key flags	2024-11-05 14:00:47 -08:00
transparent_file.cc	cleanup: remove unconditional #ifdef's	2024-11-05 14:00:47 -08:00
transparent_file.h	perfschema memory related instrumentation changes	2020-03-10 19:24:22 +01:00