DB/Search
* add more indizes to large tables for cols used in lookups
* drop multi-column indizes on spell as they are not utilized by mysql
* add and use fulltext indizes for names of items, spells, quests, creatures & objects
could add more, but is it really necessary?
* limitations
- still need a solution for race/class/spellFamily masks cols that are used as such
- fulltext indizes in boolean mode cant partial match the end of a word.
reverse name cols and search and match back to front like that..? blows up db size even more though
(+trike* : "stormstrike" => +ekirt* : "ekirtsmrots")
This commit is contained in:
parent
a89eef5736
commit
7616ec25fc
13 changed files with 373 additions and 78 deletions
|
|
@ -178,7 +178,7 @@ class GameObjectListFilter extends Filter
|
|||
|
||||
// name
|
||||
if ($_v['na'])
|
||||
if ($_ = $this->tokenizeString(['name_loc'.Lang::getLocale()->value]))
|
||||
if ($_ = $this->buildMatchLookup(['name_loc'.Lang::getLocale()->value]))
|
||||
$parts[] = $_;
|
||||
|
||||
return $parts;
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue