public inbox for [email protected]  

help / color / mirror / Atom feed

From: Robert Treat <[email protected]>
To: [email protected]
Cc: Dave Page <[email protected]>
Cc: Joshua D. Drake <[email protected]>
Cc: Devrim GUNDUZ <[email protected]>
Subject: Re: [Fwd: [BUGS] BUG #2560: Web page documentation hard
Date: Wed, 2 Aug 2006 13:33:22 -0400
Message-ID: <[email protected]> (raw)
In-Reply-To: <E7F85A1B5FF8D44C8A1AF6885BC9A0E40154C3D4@ratbert.vale-housing.co.uk>
References: <E7F85A1B5FF8D44C8A1AF6885BC9A0E40154C3D4@ratbert.vale-housing.co.uk>

On Wednesday 02 August 2006 11:18, Dave Page wrote:
> > -----Original Message-----
> > From: [email protected]
> > [mailto:[email protected]] On Behalf Of Joshua D. Drake
> > Sent: 02 August 2006 15:35
> > To: Devrim GUNDUZ
> > Cc: [email protected]
> > 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

view thread (13+ messages)  latest in thread

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: [email protected]
  Cc: [email protected], [email protected], [email protected], [email protected]
  Subject: Re: [Fwd: [BUGS] BUG #2560: Web page documentation hard
  In-Reply-To: <[email protected]>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox