MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
content-class: urn:content-classes:message
Subject: Re: Archives Search Broken
Date: Mon, 8 Mar 2004 16:40:44 -0000
Message-ID: <03AF4E498C591348A42FC93DEA9661B889F5CB@mail.vale-housing.co.uk>
Thread-Topic: [pgsql-www] Archives Search Broken
Thread-Index: AcQFKxnJFpLKn+NWQiyU8owcSyqejQAAMvRw
From: "Dave Page" <dpage@vale-housing.co.uk>
To: <josh@agliodbs.com>, <pgsql-www@postgresql.org>

=20

> -----Original Message-----
> From: Josh Berkus [mailto:josh@agliodbs.com]=20
> Sent: 08 March 2004 16:33
> To: Dave Page; pgsql-www@postgresql.org
> Subject: Re: [pgsql-www] Archives Search Broken
>=20
> Dave,
>=20
> > Though strangely it now seems to work...
>=20
> I still get nothing.  I've tried on both Konqueror & Firefox=20
> in case it's a=20
> browser issue.   Odd thing is, the search returns in about=20
> 0.5 seconds ...=20
> which is *awfully* fast considering I'm on wireless.   It's=20
> like it's not=20
> even running a search, just immediately returning "no results".
>=20
> AHA!   Found the problem, I think.   I was assuming that "in=20
> the last month"=20
> meant "in the last 30 days".    I think ASPSeek interprets=20
> "in the last=20
> month" to mean *this* month, i.e. March.   This would explain=20
> the results I'm=20
> getting for several queries.

In addition it may take a week or so for new posts to get indexed. There
is a mechanism for feeding new data directly into the index using an XML
data feed, however this will take significant work to implement for the
archives. In the meantime there is a simple weekly index cycle.

Regards, Dave.