Support graph-oriented indexing #95
Labels
No labels
A-build
A-cli
A-core
A-design
A-edn
A-ffi
A-query
A-sdk
A-sdk-android
A-sdk-ios
A-sync
A-transact
A-views
A-vocab
P-Android
P-desktop
P-iOS
bug
correctness
dependencies
dev-ergonomics
discussion
documentation
duplicate
enhancement
enquiry
good first bug
good first issue
help wanted
hygiene
in progress
invalid
question
ready
size
speed
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: greg/mentat#95
Loading…
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Pull expressions allow for recursion. One could also write rules, or even regular queries, that do path traversal over attributes.
We should consider whether there are any indexing options to expose to consumers that would help Datomish efficiently answer these queries. For example, a transitive closure index on an attribute would, at the cost of materializing and maintaining the transitive closure matrix/list, turn a recursive SQL join into a simple lookup, and also exposes minimum distance functions cheaply.
This is one example of a set of ways in which Datomish might support graph queries and other kinds of operations at a higher level of abstraction, just as
:fulltext true
does for full-text search. We should be on the lookout for more.