This repository has been archived by the owner on Sep 12, 2018. It is now read-only.
[query] Exploit AVET and VAET indexes in query engine #757
Labels
A-query
Issues or requests for query capabilities.
The SQLite schema defining the datoms table (and the indexes upon it) specifies the AVET and VAET indexes as partial: see https://github.com/mozilla/mentat/blob/master/db/src/db.rs#L180-L181 and https://github.com/mozilla/mentat/blob/master/db/src/db.rs#L183-185. The only way the SQLite query engine can exploit those indexes is if the produced SQL constrains the query, in some way to have the relevant
index_{avet,vaet}
columns set -- and we don't do that right now.There's a similar but technically distinct case that we do support. The
:db/fulltext true
case is managed asindex_fulltext
and as a separate table. If we wanted to, we could manage the partial indexes as separate tables manually. It's not clear what is the more desirable SQLite schema.The text was updated successfully, but these errors were encountered: