From: | "Dave Page" <dpage(at)vale-housing(dot)co(dot)uk> |
---|---|
To: | "Joshua D(dot) Drake" <jd(at)commandprompt(dot)com>, "Devrim GUNDUZ" <devrim(at)commandprompt(dot)com> |
Cc: | <pgsql-www(at)postgresql(dot)org> |
Subject: | Re: [Fwd: [BUGS] BUG #2560: Web page documentation hard |
Date: | 2006-08-02 15:18:31 |
Message-ID: | E7F85A1B5FF8D44C8A1AF6885BC9A0E40154C3D4@ratbert.vale-housing.co.uk |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-www |
> -----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.
Regards, Dave.
From | Date | Subject | |
---|---|---|---|
Next Message | Robert Treat | 2006-08-02 17:33:22 | Re: [Fwd: [BUGS] BUG #2560: Web page documentation hard |
Previous Message | Joshua D. Drake | 2006-08-02 14:35:26 | Re: [Fwd: [BUGS] BUG #2560: Web page documentation hard |