Include worked example with a manually ordered list #244
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#244
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?
Datomic and Mentat are primarily set oriented, but there's some data that really wants to be ordered and the order is arbitrary. Datomic users tend to handle this with a "transaction function" that atomically updates order attributes during a transaction. (See, for example, https://augustl.com/blog/2013/ordering_cardinality_many_in_datomic/.) That approach is probably possible in Mentat, but it's not easy to arrange right now. This is mostly a TODO item for @rnewman to set down his thoughts on what we should do here.