Ian Harding wrote:
> On 5/31/07, Joshua D. Drake <jd@commandprompt.com> wrote:
>> Ian Harding wrote:
>> > tsearch indexes have to reside in the table where the data is, for the
>> > automagical functions that come with it to work. You can define a
>> > view that joins the tables, then search each of the index columns for
>> > the values you are looking for.
>>
>> No they don't.
>>
>
> Hm? Allow me to clarify.
>
> To the best of my knowledge, and in my limited experience, the
> tsearch2() trigger function provided with tsearch will only index
> fields present in the table upon which it is created, in an index
> column present in the table upon which it is created. If I am
> incorrect in this assessment I would be glad to be corrected.
>
> Of course, custom triggers can be written to do anything from soup to nuts.
Yes you would need a trigger to keep a separate search table but you can
certainly join on that table for selects.
J
>
> - Ian A. Harding
>
>> Joshua D. Drake
>>
>>
>
> ---------------------------(end of broadcast)---------------------------
> TIP 4: Have you searched our list archives?
>
> http://archives.postgresql.org/
>
--
=== The PostgreSQL Company: Command Prompt, Inc. ===
Sales/Support: +1.503.667.4564 || 24x7/Emergency: +1.800.492.2240
Providing the most comprehensive PostgreSQL solutions since 1997
http://www.commandprompt.com/
Donate to the PostgreSQL Project: http://www.postgresql.org/about/donate
PostgreSQL Replication: http://www.commandprompt.com/products/
