Re: [Fwd: [BUGS] BUG #2560: Web page documentation hard

On Wednesday 02 August 2006 11:18, Dave Page wrote:
> > -----Original Message-----
> > From: pgsql-www-owner(at)postgresql(dot)org
> > [mailto:pgsql-www-owner(at)postgresql(dot)org] On Behalf Of Joshua D. Drake
> > Sent: 02 August 2006 15:35
> > To: Devrim GUNDUZ
> > Cc: pgsql-www(at)postgresql(dot)org
> > Subject: Re: [pgsql-www] [Fwd: [BUGS] BUG #2560: Web page
> > documentation hard
> >
> > >> I'm trying to look up the SQL keyword 'in' using the
> >
> > postgresql.org web
> >
> > >> search function.
> >
> > Well isn't that interesting. He has a valid point. I think
> > Tsearch can
> > pick which words it won't ignore so we could take IN SELECT
> > JOIN things
> > like that out, however that would take changing our infrastructure.
>
> ASPSeek can as well (they're called stopwords) but it won't help in this
> case because even if we don't ignore IN et al. it'll still match
> virtually every page.
>

What would be nice would be to have a first level of human specified keywords
that return specific information, above and beyond the general search. This
could operate similarly to rtfm_please on irc or my rtfmbot on AIM. This way
when someone searches on something like IN, we can say "you're probably
looking for this --> link" If there are general search results, we could
show them after the pre-spelected links.

--
Robert Treat
Build A Brighter LAMP :: Linux Apache {middleware} PostgreSQL