Confirmed users
574
edits
DXR Storages: Difference between revisions
Jump to navigation
Jump to search
Factor up update/delete support.
(trilite is coring for me.) |
(Factor up update/delete support.) |
||
| Line 5: | Line 5: | ||
* Contributors have trouble building it and messing with <code>LD_LIBRARY_PATH</code>. | * 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. | * 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. | Here are some alternatives. Let's go shopping. | ||
| Line 16: | Line 17: | ||
* Parallelization of even single queries | * Parallelization of even single queries | ||
* Redundancy | * Redundancy | ||
* 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.) | * 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 | * Suggesters for "did you mean" and autocomplete | ||
| Line 35: | Line 35: | ||
* An easy port from our existing relational-based storage | * An easy port from our existing relational-based storage | ||
== Trilite Unique Advantages == | == Trilite Unique Advantages == | ||