Firefox/Projects/FTS and Awesomebar: Difference between revisions

Jump to navigation Jump to search
→‎Intro: Remove paragraph on i18n from the Intro, since that's really not the goal
(→‎Intro: Remove paragraph on i18n from the Intro, since that's really not the goal)
Line 4: Line 4:


SQLite supports indexed full text search (FTS) through its fts extensions.  Indexed FTS makes text searches fast:  Rather than looking at every record in the database to see if it contains a search string, target records are found by comparing the search string against an index.
SQLite supports indexed full text search (FTS) through its fts extensions.  Indexed FTS makes text searches fast:  Rather than looking at every record in the database to see if it contains a search string, target records are found by comparing the search string against an index.
But the fts extensions aren't by default suitable for international text.  This project will try to make them suitable so we can use FTS to improve Firefox features that rely on Storage text searches for all of our users.


A good first target feature is the awesomebar.  It is highly visible, and since it makes extensive use of text searches, it stands to benefit from this work.
A good first target feature is the awesomebar.  It is highly visible, and since it makes extensive use of text searches, it stands to benefit from this work.


Note that full text search does not mean that we store the entire text of pages.  We will use it to store page titles, URLs, tags, etc., as we already do now, only lookup will be fast.
(Note that full text search does not mean that we store the entire text of pages.  We will use it to store page titles, URLs, tags, etc., as we already do now, only lookup will be fast.)


* Champion, lead: adw
* Champion, lead: adw
Confirmed users
764

edits

Navigation menu