| |
1 |
1 |
<html> <head> <title>TSEARCH2 PostgreSQL FtsEngineDriver for OpenACS |
| |
2 |
2 |
5.x</title> </head> <h1>TSEARCH2 PostgreSQL FtsEngineDriver for |
| |
3 |
3 |
OpenACS 5.x</h1> <h2>Installing</h2> You'll need PostgreSQL 7.3 or |
| |
4 |
4 |
newer. The tsearch2 from contrib needs to be compiled. In addition |
| |
5 |
5 |
tsearch2.sql needs to be loaded into your database. In addition be |
| |
6 |
6 |
sure to mount the Search package somewhere. The indexer will not run |
| |
7 |
7 |
is Search is not mounted. The FtsEngineDriver parameter of the |
| |
8 |
8 |
search package must be changes to "tsearch2-driver". |
| |
9 |
9 |
|
| |
10 |
10 |
<h2>Using</h2> |
| |
11 |
11 |
If you install tsearch2-driver and mount search, go ahead and add |
| |
12 |
12 |
some content. Weblogger or edit-this-page will generate indexed |
| |
13 |
13 |
cotent. I had to manually load lars-blogger-sc-create.sql to get |
| |
14 |
14 |
Weblogger to register the service contract implementation to index |
| |
15 |
15 |
the content. After that it worked fine. |
| |
16 |
16 |
|
| |
|
17 |
<h2>Index old content</h2> |
| |
|
18 |
If your old content has not been indexed before (e.g. because you had no |
| |
|
19 |
search package mounted before), all is fine. Otherwise you have to inform the |
| |
|
20 |
search package to reindex.<br> |
| |
|
21 |
insert into search_observer_queue ( select my_id, now(),'INSERT' from |
| |
|
22 |
my_table);<br> |
| |
|
23 |
For forums and ETP this looks like: |
| |
|
24 |
<blockquote> |
| |
|
25 |
<pre> |
| |
|
26 |
insert into search_observer_queue (select message_id, now(), 'INSERT' from forums_messages); |
| |
|
27 |
insert into search_observer_queue (select live_revision, now(), 'INSERT' from ( |
| |
|
28 |
select live_revision from cr_items where content_type = 'etp_page_revision') etp); |
| |
|
29 |
</pre> |
| |
|
30 |
</blockquote> |
| |
17 |
31 |
<h2>Features</h2> |
| |
18 |
32 |
This version includes only the most basic features to prove that |
| |
19 |
33 |
tsearch2 can be used for indexing. There are many configuration |
| |
20 |
34 |
options that will be avaialble as parameters in the future. It is |
| |
21 |
35 |
also clear that the current service contract definitions are not |
| |
22 |
36 |
flexible enough to work well with every possible search driver, so |
| |
23 |
37 |
some features may not be available until after the search package is |
| |
24 |
38 |
also updated. |
| |
25 |
39 |
|
| |
26 |
40 |
Dave Bauer dave@thedesignexperience.org 2004-06-05 |
