This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2019-10-12
Channels
- # aleph (1)
- # announcements (1)
- # beginners (54)
- # calva (11)
- # clojure (55)
- # clojure-france (1)
- # clojure-italy (4)
- # clojure-spec (10)
- # clojure-uk (7)
- # clojurescript (3)
- # cursive (3)
- # data-science (8)
- # datomic (10)
- # emacs (1)
- # fulcro (21)
- # graalvm (2)
- # jobs (1)
- # kaocha (1)
- # nrepl (1)
- # nyc (1)
- # other-languages (5)
- # reitit (8)
- # rum (5)
- # shadow-cljs (84)
- # spacemacs (2)
- # sql (20)
- # testing (3)
- # vim (1)
when perform a db/history
query, how can I get only datoms that have the same db/txInstant
?
db/txInstant
is an attribute of a transactions so I'm guessing you want to access all datoms asserted by a transaction?
yes, that's right. When performing db/history and filtering for a single datom, I find the entity that I want to but it brings back all other datoms of the history. I would like to get back only the datoms asserted by the transaction of the datom that I am using to filter the query. [confusing? :/]
You should be able to filter like this:
[?tx :db/txInstant <your-instant>]
[?e ?a ?v ?tx ?op]
If you have a specific tx and you want to know what happened in it, use the log and tx-range instead
Yes, but @UBSREKQ5Q said they know what entity they want to so I assumed ?e
is already bound to something. But if not, @U09R86PA4 is right, do not do that 🙂
What happens if you update the compute cluster before the storage as your told not to here: https://docs.datomic.com/cloud/operation/upgrading.html#storage-and-compute
What is the state of art of unifying Datomic schema with clojure.spec