From af100642e17f887b1d974066491c201f107c939d Mon Sep 17 00:00:00 2001
From: zYne <zYne@625475ce-881a-0410-a577-b389adb331d8>
Date: Thu, 2 Aug 2007 00:35:56 +0000
Subject: [PATCH]
---
manual/new/docs/en/searching.txt | 8 +++-----
1 file changed, 3 insertions(+), 5 deletions(-)
diff --git a/manual/new/docs/en/searching.txt b/manual/new/docs/en/searching.txt
index 2211ea469..835eb3c01 100644
--- a/manual/new/docs/en/searching.txt
+++ b/manual/new/docs/en/searching.txt
@@ -37,13 +37,12 @@ class NewsItem extends Doctrine_Record
}
public function setUp()
{
- $this->loadTemplate('Doctrine_Search_Template',
- array('fields' => array('title', 'content')));
+ $this->actAs('Searchable', array('fields' => array('title', 'content')));
}
}
</code>
-Here we tell Doctrine that NewsItem class uses Doctrine_Search_Template and fields title and content are marked as fulltext indexed fields. This means that everytime a NewsItem is added or updated Doctrine will:
+Here we tell Doctrine that NewsItem class acts as searchable (internally Doctrine loads Doctrine_Template_Searchable) and fields title and content are marked as fulltext indexed fields. This means that everytime a NewsItem is added or updated Doctrine will:
1. Update the inverse search index or
2. Add new pending entry to the inverse search index (its efficient to update the inverse search index in batches)
@@ -62,5 +61,4 @@ The structure of the inverse index Doctrine uses is the following:
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.
++ Index building
-
-
+++ Query language