Changes

Jump to: navigation, search

DXR Storages

49 bytes removed, 20:55, 21 February 2014
Factor up update/delete support.
* Contributors have trouble building it and messing with <code>LD_LIBRARY_PATH</code>.
* It cores on my development VM (but not for anybody else) when I pass it a bad regex, and I don't know why.
* We haven't implemented delete or update support in it, which we'd need for incremental indexing.
Here are some alternatives. Let's go shopping.
* Parallelization of even single queries
* Redundancy
* Already-implemented update and delete support (which trilite is missing and which we'd need for incremental indexing)
* Caching of intermediate filter results. (It will transparently store the set of, say, all *.cpp files as a bitmap for quick set operations later. This means that common compound queries will likely be much faster than in any RDBMS.)
* Suggesters for "did you mean" and autocomplete
* An easy port from our existing relational-based storage
* Update and delete support
== Trilite Unique Advantages ==
Confirm
574
edits

Navigation menu