Transacting a refid not corresponding with any datom eids should fail?
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 30/100
Research direction
Review the transaction example alongside the README's documented Datomic differences and the related issues #166 and #187. Reproduce the differing behavior, then determine whether the intended result is Datomic parity or a broader wiki comparison; done should be either a tested behavior change or a comprehensive, maintained differences list.
Written by the indexing model from the issue text.
Description
The following transaction fails in Datomic, but not DataScript:
[[:db/add (d/tempid :db.part/user -1) :some.ref/attr (d/tempid :db.part/user -2)]]
This means a little bit of extra work automatically syncing Datomic and Datascript, at least if you want to try to catch and handle quirks like this.
There are obviously plenty of other points where DataScript is intentionally different from Datomic, and if this isn't something you want to move towards parity on, I'm fine with that. But perhaps we should have a more comprehensive list of subtle behavior differences like this on the wiki? This could start off with what's at the bottom of the README, but try to encompass a broader range of subtler differences, such as #166, #187, etc. I'm happy to start this if you like.
- Dominant language
- Clojure
- Stars
- 5.8k
- Forks
- 318
- PR merge metrics
- No merged PRs in 30d
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from tonsky/datascript
-
Difficulty 4/5 3-5 days Newbie friendliness 42/100
tonsky/datascript#498 · 1 comment ·
-
Difficulty 5/5 Over a week Newbie friendliness 10/100
tonsky/datascript#489 ·
-
Stack overflow when transacting :db.type/tupleAttrs with a :db.type/ref attr through :db.fn/call Open
Difficulty 4/5 3-5 days Newbie friendliness 35/100
tonsky/datascript#483 · 2 comments ·
-
Difficulty 4/5 3-5 days Newbie friendliness 35/100
tonsky/datascript#470 · 1 comment ·
-
Difficulty 4/5 3-5 days Newbie friendliness 35/100
tonsky/datascript#441 · 1 comment · 3 reactions ·
All issues in tonsky/datascript
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
.Needs Triage .Team/UXWest Priority:P3 Type:New Feature
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
-
Difficulty 1/5 Under an hour Newbie friendliness 90/100
-
Difficulty 1/5 Under an hour Newbie friendliness 88/100
-
needs triage
Difficulty 1/5 Under an hour Newbie friendliness 90/100