6df9145446
* do not use stopwords in fulltext search apparentyl there is a bug in innodb where including stopwords in a search causes the lookup to fail entirely. e.g. innodb_ft_enable_stopword must be disabled when the index is edited (rows are added/removed) * don't create a MATCH AGAINST search from empty search strings after sanitization * drop fulltext indizes for locale zhCN logographic languages need special treatment, which handling may differ by db provider * use LIKE search by default for locale zhCN. Added config option to use fulltext if supported by db.
16 lines
674 B
SQL
16 lines
674 B
SQL
ALTER TABLE `aowow_creature` DROP INDEX `idx_name4`;
|
|
ALTER TABLE `aowow_items` DROP INDEX `idx_name4`;
|
|
ALTER TABLE `aowow_objects` DROP INDEX `idx_name4`;
|
|
ALTER TABLE `aowow_quests` DROP INDEX `idx_name4`;
|
|
ALTER TABLE `aowow_spell` DROP INDEX `idx_name4`;
|
|
|
|
SET SESSION innodb_ft_enable_stopword = OFF;
|
|
|
|
OPTIMIZE TABLE `aowow_spell`;
|
|
OPTIMIZE TABLE `aowow_quests`;
|
|
OPTIMIZE TABLE `aowow_creature`;
|
|
OPTIMIZE TABLE `aowow_items`;
|
|
OPTIMIZE TABLE `aowow_objects`;
|
|
|
|
REPLACE INTO `aowow_config` VALUES
|
|
('logographic_ft_search', '0', '0', 1, 0x484, 'enables fulltext search for logographic languages (CN, KR, TW). The database MUST support this (i.e. MySQL implements ngram)');
|