Dominique Devienne wrote on Monday, July 15, 2019 2:41 AM >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). That sounds really intriguing- does it significantly speed up queries coming in through the SQLite engine? Or the speed bump is only if accessing from the C++-native side? Is there any literature out there or tips you can share that can flatten the learning curve? Thanks Erik ---------------------------------------------------------------------- This message, and any attachments, is for the intended recipient(s) only, may contain information that is privileged, confidential and/or proprietary and subject to important terms and conditions available at http://www.bankofamerica.com/emaildisclaimer. If you are not the intended recipient, please delete this message. _______________________________________________ sqlite-users mailing list sqlite-users@mailinglists.sqlite.org http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
