Add storage search foundation
This commit is contained in:
@@ -127,6 +127,8 @@ Definition of done:
|
||||
|
||||
Goal: make hundreds of thousands or millions of entries feel normal.
|
||||
|
||||
Current foundation note: [Storage And Search Foundation](docs/storage-search-foundation.md).
|
||||
|
||||
Tasks:
|
||||
|
||||
- Keep SQLite for desktop and private/single-user workflows.
|
||||
@@ -135,6 +137,7 @@ Tasks:
|
||||
- Add proper indexes for translation id, book/chapter/verse, Strong's number, lemma, resource id, place id, and attachment relationships.
|
||||
- Add full-text search through SQLite FTS5 or a compatible indexed search layer.
|
||||
- Avoid loading entire large resources into the browser when a chapter, page, verse, Strong's entry, or search result can be loaded on demand.
|
||||
- Keep the UI pointed at shared query/search interfaces so JSON packages, Tauri SQLite, hosted SQLite, and future server search can be swapped without rewriting the reader.
|
||||
|
||||
Definition of done:
|
||||
|
||||
|
||||
Reference in New Issue
Block a user