On Mon, Jul 15, 2019 at 8:24 AM Barry <smith.bar...@gmail.com> wrote:
> For performance reasons I've had to write custom code where I have changing > data that I need to keep 'indices' on. I found it very difficult to get it > right, and very fragile. If I didn't need the performance, I would much > rather have used an in-memory DB (sadly it just wasn't fast enough). > That's when you reach for virtual tables (and their "virtual indices"). I.e. you keep your data in native data-structures (Boost.MultiIndex in my case), and just provide a SQLite view of it. Much faster than "pure-in-Memory" with SQLite-managed pager-backed B-tree tables. Steep learning curve, especially for the indexing part, but the results are well worth it IMHO. Which can be freely mixed with "real" tables having "real" indexes (in the in-memory DB). FWIW. --DD _______________________________________________ sqlite-users mailing list sqlite-users@mailinglists.sqlite.org http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
