New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Support full text indexes #44

Open
inexorabletash opened this Issue Oct 7, 2015 · 5 comments

Comments

Projects
None yet
4 participants
@inexorabletash
Member

inexorabletash commented Oct 7, 2015

Either directly support full text indexes, or provide the primitives necessary to build them, which might include prefix-based searching, expression indexing, etc.

Imported from https://www.w3.org/2008/webapps/wiki/IndexedDatabaseFeatures

@inexorabletash

This comment has been minimized.

Show comment
Hide comment
@inexorabletash

inexorabletash Oct 7, 2015

Member

i.e. may just be #33

Member

inexorabletash commented Oct 7, 2015

i.e. may just be #33

@nolanlawson

This comment has been minimized.

Show comment
Hide comment
@nolanlawson

nolanlawson Sep 22, 2016

Member

+1, big missing feature between WebSQL and IDB.

I agree this should be closed though in favor of #33 (w/ worklets). It ought to be out-of-scope to define particular stemmers for particular languages (e.g. Porter/English by default, as SQLite does). The worklet solution neatly allows e.g. Lunrjs to create their own. Folks will also inevitably want very complex stemmer functionality (e.g. "parse this field both as French and as English, index the union of all tokens") and such things should be solved in userland IMO.

Unsolved by #33 however: how to implement a scoring function, e.g. TF-IDF, DisMax, etc.

Member

nolanlawson commented Sep 22, 2016

+1, big missing feature between WebSQL and IDB.

I agree this should be closed though in favor of #33 (w/ worklets). It ought to be out-of-scope to define particular stemmers for particular languages (e.g. Porter/English by default, as SQLite does). The worklet solution neatly allows e.g. Lunrjs to create their own. Folks will also inevitably want very complex stemmer functionality (e.g. "parse this field both as French and as English, index the union of all tokens") and such things should be solved in userland IMO.

Unsolved by #33 however: how to implement a scoring function, e.g. TF-IDF, DisMax, etc.

@inexorabletash

This comment has been minimized.

Show comment
Hide comment
@inexorabletash

inexorabletash Sep 28, 2016

Member

If you're watching this issue...

One of the primitives necessary for building full text search on top of indexes is text segmentation. @littledan has a proposal for adding this to ECMA-402 (the ECMAScript Intl object). He'd love feedback:

Member

inexorabletash commented Sep 28, 2016

If you're watching this issue...

One of the primitives necessary for building full text search on top of indexes is text segmentation. @littledan has a proposal for adding this to ECMA-402 (the ECMAScript Intl object). He'd love feedback:

@EloB

This comment has been minimized.

Show comment
Hide comment
@EloB

EloB Dec 30, 2017

This is one of the big reason why I rather use WebSQL instead of Indexeddb.

EloB commented Dec 30, 2017

This is one of the big reason why I rather use WebSQL instead of Indexeddb.

@aphillips

This comment has been minimized.

Show comment
Hide comment
@aphillips

aphillips Dec 30, 2017

@nolanlawson and @inexorabletash have identified a couple of the challenges with implementing FTS: it's language sensitive, and open source provides imperfect solutions even for common languages. That's not an argument against it as a desirable feature, just a practical observation.

aphillips commented Dec 30, 2017

@nolanlawson and @inexorabletash have identified a couple of the challenges with implementing FTS: it's language sensitive, and open source provides imperfect solutions even for common languages. That's not an argument against it as a desirable feature, just a practical observation.

@w3c w3c deleted a comment from Shawndrea Jan 9, 2018

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment