[tx] Consider using cache
module for resolving lookup-refs and upserts in transactor
#235
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#235
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?
Long after the initial transactor implementation was set down, Mentat grew a nice cache abstraction; it's in https://github.com/mozilla/mentat/blob/master/db/src/cache.rs. The transactor does a few things right now that are "hand rolled": resolving lookup-refs and upserts. Both of those could be expressed as populating caches from
[a v]
toe
. It might be nice to unify on the cache abstraction more generally, minimizing hand rolled SQL queries and special purpose munging.