X-Original-To: pgsql-www-postgresql.org@postgresql.org Received: from localhost (wm.hub.org [200.46.204.128]) by postgresql.org (Postfix) with ESMTP id 7F29E9FA68D for ; Wed, 2 Aug 2006 14:33:51 -0300 (ADT) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.128]) (amavisd-new, port 10024) with ESMTP id 89633-02 for ; Wed, 2 Aug 2006 17:33:29 +0000 (UTC) X-Greylist: from auto-whitelisted by SQLgrey- Received: from eastrmmtao01.cox.net (eastrmmtao01.cox.net [68.230.240.38]) by postgresql.org (Postfix) with ESMTP id D76CF9FA4A8 for ; Wed, 2 Aug 2006 14:33:28 -0300 (ADT) Received: from [192.168.0.8] (really [68.226.0.201]) by eastrmmtao01.cox.net (InterMail vM.6.01.06.01 201-2131-130-101-20060113) with ESMTP id <20060802173326.WXSZ12077.eastrmmtao01.cox.net@[192.168.0.8]>; Wed, 2 Aug 2006 13:33:26 -0400 From: Robert Treat To: pgsql-www@postgresql.org Subject: Re: [Fwd: [BUGS] BUG #2560: Web page documentation hard Date: Wed, 2 Aug 2006 13:33:22 -0400 User-Agent: KMail/1.9.1 Cc: "Dave Page" , "Joshua D. Drake" , "Devrim GUNDUZ" References: In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200608021333.22917.xzilla@users.sourceforge.net> X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=3.816 tagged_above=0 required=5 tests=SPF_HELO_SOFTFAIL, SPF_SOFTFAIL X-Spam-Level: *** X-Archive-Number: 200608/12 X-Sequence-Number: 10403 On Wednesday 02 August 2006 11:18, Dave Page wrote: > > -----Original Message----- > > From: pgsql-www-owner@postgresql.org > > [mailto:pgsql-www-owner@postgresql.org] On Behalf Of Joshua D. Drake > > Sent: 02 August 2006 15:35 > > To: Devrim GUNDUZ > > Cc: pgsql-www@postgresql.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