| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | "Dave Page" <dpage(at)vale-housing(dot)co(dot)uk> |
| Cc: | "Richard Huxton" <dev(at)archonet(dot)com>, "Robert Bernier" <robert(dot)bernier5(at)sympatico(dot)ca>, pgsql-www(at)postgresql(dot)org |
| Subject: | Re: [Fwd: [BUGS] BUG #2560: Web page documentation hard |
| Date: | 2006-08-02 20:43:09 |
| Message-ID: | 20421.1154551389@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-www |
"Dave Page" <dpage(at)vale-housing(dot)co(dot)uk> writes:
>> But what strikes me is the idea of teaching the search engine not to
>> ignore stopwords that are marked as <indexterm>'s ...
> We tell it what to ignore, not the other way round. Besides, the problem as I understood it was that a search for 'IN' returns virtually every page (as one might expect) which is little help when looking for IN the keyword.
Right, so half of the problem is that IN should be considered a stopword
and isn't. But after we fix that, it won't be found anywhere. I
suggest that we want the search to find the pages on which IN (or any
other stopword) appears as an <indexterm>, and not elsewhere.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Dave Page | 2006-08-02 21:33:56 | Re: [Fwd: [BUGS] BUG #2560: Web page documentation hard |
| Previous Message | Dave Page | 2006-08-02 20:39:57 | Re: [Fwd: [BUGS] BUG #2560: Web page documentation hard |