Re: [IndexedDB] Full text indexing

We haven't looked at it much since there were many bigger issues to be
resolved first.  But now that those issues are largely resolved, maybe now
is a good time to start talking about this seriously.

I think most people were down on the idea of adding complete "full text
search" because it'd be a _lot_ of API surface area.  But, everyone I've
talked to seems to think that native "inverted index" support + JS for the
rest should be a reasonable compromise for v1.

Hopefully by end of year, we'll be ready to start experimenting with such
support in Chrome/WebKit.  If someone wanted to push this forward on the
spec side or in another implementation in the mean time, that'd be great
though.

J

On Mon, Aug 23, 2010 at 11:03 AM, Nathan Kitchen <w3c@nathankitchen.com>wrote:

> Hi.
>
> Just wondering if anyone could take a few moments to provide an update on
> the state of full-text indexing in IndexedDB?
>
> A quick google indicated that the question had been raised before, Jeremy
> Orlow suggesting support for inverted indexes (back in February) and there
> was a reference to ongoing discussions on the subject in June.
>
> The current working draft doesn't appear to mention inverted indexes or
> full text, and it was updated fairly recently.
>
> Cheers.
>
>