X-Original-To: pgsql-www-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [200.46.204.2]) by svr1.postgresql.org (Postfix) with ESMTP id EA1DDD1B55C for ; Mon, 8 Mar 2004 19:06:06 +0000 (GMT) Received: from svr1.postgresql.org ([200.46.204.71]) by localhost (neptune.hub.org [200.46.204.2]) (amavisd-new, port 10024) with ESMTP id 85881-01 for ; Mon, 8 Mar 2004 15:06:04 -0400 (AST) Received: from bramble.mmrd.com (unknown [65.217.53.66]) by svr1.postgresql.org (Postfix) with ESMTP id 7F265D1B51F for ; Mon, 8 Mar 2004 15:06:02 -0400 (AST) Received: from thorn.mmrd.com (thorn.mmrd.com [172.25.10.100]) by bramble.mmrd.com (8.12.8/8.12.8) with ESMTP id i28IcZcM019691; Mon, 8 Mar 2004 13:38:35 -0500 Received: from gnvex001.mmrd.com (gnvex001.mmrd.com [192.168.3.55]) by thorn.mmrd.com (8.11.6/8.11.6) with ESMTP id i28J5tl24039; Mon, 8 Mar 2004 14:05:55 -0500 Received: from camel.mmrd.com ([172.25.5.213]) by gnvex001.mmrd.com with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2657.72) id FVMAWRMR; Mon, 8 Mar 2004 14:05:53 -0500 Subject: Re: Archives Search Broken From: Robert Treat To: Josh Berkus Cc: Dave Page , pgsql-www@postgresql.org In-Reply-To: <200403080832.42105.josh@agliodbs.com> References: <03AF4E498C591348A42FC93DEA9661B889F5BA@mail.vale-housing.co.uk> <200403080832.42105.josh@agliodbs.com> Content-Type: text/plain Content-Transfer-Encoding: 7bit X-Mailer: Ximian Evolution 1.0.8 Date: 08 Mar 2004 14:05:54 -0500 Message-Id: <1078772755.2784.211.camel@camel> Mime-Version: 1.0 X-Virus-Scanned: by amavisd-new at postgresql.org X-Archive-Number: 200403/61 X-Sequence-Number: 3877 On Mon, 2004-03-08 at 11:32, Josh Berkus wrote: > Dave, > > > Though strangely it now seems to work... > > I still get nothing. I've tried on both Konqueror & Firefox in case it's a > browser issue. Odd thing is, the search returns in about 0.5 seconds ... > which is *awfully* fast considering I'm on wireless. It's like it's not > even running a search, just immediately returning "no results". > > AHA! Found the problem, I think. I was assuming that "in the last month" > meant "in the last 30 days". I think ASPSeek interprets "in the last > month" to mean *this* month, i.e. March. This would explain the results I'm > getting for several queries. > I've been bitten by that before myself...though I didn't know it since I gave up and went to a different search engine after a couple of attempts. I tend to agree with Josh's interpretation that in the last month implies the last 30 days or some such similar timeframe. Can we change the wording on that to maybe "in the current month" or "in this month" or if we can get fancy just print the month name... "in March".. though we'd need to rebuild any referencing pages once a month.... Robert Treat -- Build A Brighter Lamp :: Linux Apache {middleware} PostgreSQL