| [ < ] | [ > ] | [ << ] | [ Up ] | [ >> ] | [Top] | [Contents] | [Index] | [ ? ] |
6.1 Default full text 6.2 Real full text
| [ < ] | [ > ] | [ << ] | [ Up ] | [ >> ] | [Top] | [Contents] | [Index] | [ ? ] |
The search mechanism of Catalog is implemented using the regexp operator
of MySQL. For instance, when searching for the word foobar, the regexp used will be:
REGEXP '[[:<:]][fF][oO][oO][bB][aA][rR][[:>:]]' |
This basically means that only the isolated foobar word will be found and not the
word foobarnitz, See section Catalog search (csearch).
This method can be really slow if the catalog contains a lot of data. We are working on this.
If the encoding of the catalog is not ISO-8859-* a the query is taken to
be only one word and is searched using the SQL truncation operators,
See section Catalog configuration file.
like '%word1 word2%' |
| [ < ] | [ > ] | [ << ] | [ Up ] | [ >> ] | [Top] | [Contents] | [Index] | [ ? ] |
An automatic mechanism builds a full text index for every record in the
SQL database. The full text index contains enough information to find
which record of which table contains a specific word, See section Hook Fulcrum configuration file.
To activate the automatic indexation of a MySQL database set the hook
attribute of the mysql.conf file to either Catalog::tools::hook_mifluz or
Catalog::tools::hook_fulcrum, See section MySQL configuration file.
This mechanism currently specific to the Fulcrum full text engine and quite complex to tune.
| [ << ] | [ >> ] | [Top] | [Contents] | [Index] | [ ? ] |