Optimization: eliminate non-fulltext attributes mentioned in a fulltext expression #76

Open
opened 2020-08-06 16:54:31 +00:00 by gburd · 0 comments
gburd commented 2020-08-06 16:54:31 +00:00 (Migrated from github.com)

If the user does something simplistic, like dump in a set of potential attributes (perhaps even some that aren't present in the store!) we should eagerly drop those on the floor. If that results in an empty attribute set, the entire fulltext expression will fail to match anything, and can be optimized away into failure.

If the user does something simplistic, like dump in a set of potential attributes (perhaps even some that aren't present in the store!) we should eagerly drop those on the floor. If that results in an empty attribute set, the entire `fulltext` expression will fail to match anything, and can be optimized away into failure.
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: greg/mentat#76
No description provided.