RetailCRM-Mirror/doctrine2
1
0
Fork 0
mirror of synced 2025-02-20 22:23:14 +03:00
Code Issues Projects Releases Wiki Activity

docs for text analyzers

Browse Source
This commit is contained in:
zYne 2007-10-17 20:14:46 +00:00
parent c1c87d0287
commit 733e44e420
1 changed files with 22 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

23
manual/new/docs/en/searching.txt
View File

@ -58,7 +58,28 @@ The structure of the inverse index Doctrine uses is the following:
* **position** is the position where the keyword was found
* **[foreign_keys]** either one or multiple fields depending on the owner component (here NewsItem)
In the NewsItem example the [foreign_keys] would simply contain one field newsitem_id with foreign key references to NewsItem(id) and with onDelete => CASCADE constraint.
In the NewsItem example the [foreign_keys] would simply contain one field id with foreign key references to NewsItem(id) and with onDelete => CASCADE constraint.
++ Index building
Whenever a searchable record is being inserted into database Doctrine executes the index building procedure. The phases of this operation are:
1. Analyze the text using a Doctrine_Search_Analyzer based class
2. Insert new rows into index table for all analyzed keywords
++ Text analyzers
By default Doctrine uses Doctrine_Search_Analyzer_Standard for analyzing the text. This class performs the following things:
1. Strips out stop-keywords (such as 'and', 'if' etc.)
2. Makes all keywords lowercased
3. Replaces all non alpha-numeric marks with whitespace so that 'database' matches 'database.'
4. Replaces all quotation marks with empty strings so that "O'Connor" matches "oconnor"
You can write your own analyzer class by making a class that implements Doctrine_Search_Analyzer_Interface. This analyzer can then be applied to the search object as follows:
<code type="php">
$search->setOption('analyzer', new MyAnalyzer());
</code>
++ Query language