| From: | "Ian Harding" <harding(dot)ian(at)gmail(dot)com> |
|---|---|
| To: | "Joshua D(dot) Drake" <jd(at)commandprompt(dot)com> |
| Cc: | "Gabriel Laet" <gabriel(dot)laet(at)gmail(dot)com>, pgsql-general(at)postgresql(dot)org |
| Subject: | Re: Design Table & Search Question |
| Date: | 2007-06-01 04:22:35 |
| Message-ID: | 725602300705312122s2d7d0fb9gd12383a17dff6fce@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On 5/31/07, Joshua D. Drake <jd(at)commandprompt(dot)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.
- Ian A. Harding
> Joshua D. Drake
>
>
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Joshua D. Drake | 2007-06-01 04:30:45 | Re: Design Table & Search Question |
| Previous Message | Tom Lane | 2007-06-01 03:48:10 | Re: left outer join and values() |