Store the content of the indexed content in a database?

[Biff]

Is there a way to store the content of the indexed content in a database (instead of holding it in the RAM)? Maybe as an option (causing longer searches for contents).

Why is it that Everything sometimes uses 700 MB of RAM and often uses 3-5 GB up to 7 GB of RAM? So how is it possible that the same information (of the indexed content, etc.) suddenly only needs 700 MB RAM?

[TheBestPessimist]

This is an interesting idea: store the content in something like an SQLite with FTS?

I am talking about "content indexing" feature, not about the usual file indexing which should not be changed.

[wise_mike]

I second that, it would be great to have a fixed database, and updated only when needed. For example if one has 1000 files that are not changing, no need to reindex them each time I open the program. They can just stay in the database all the time.

[void]

Everything should only index your content once.

Alternatively, search your system index with Everything using si: