https://www.sqlite.org/fts3.html
, where it says: "Note that SQLite will process an SQL SELECT statement tree against an FTS table in three phases: ... The final phase rewrite the query from the inner join into an outer join.", and
https://www.sqlite.org/indexing_ft_only.html
, where it says: "the bookwith table can be faster if you omit the where clause and just ask for the full-text results for all of rows of bookwith." ?
And which is more useful for general-purpose website full-text search -- FTS, or a table with a _column called sqlite_fts_index=... ?
https://www.sqlite.org/fts3.html
, where it says: "Note that SQLite will process an SQL SELECT statement tree against an FTS table in three phases: ... The final phase rewrite the query from the inner join into an outer join.", and
https://www.sqlite.org/indexing_ft_only.html
, where it says: "the bookwith table can be faster if you omit the where clause and just ask for the full-text results for all of rows of bookwith." ?
And which is more useful for general-purpose website full-text search -- FTS, or a table with a _column called sqlite_fts_index=... ?