This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2021-05-04
Channels
- # announcements (1)
- # asami (61)
- # babashka (71)
- # beginners (170)
- # biff (1)
- # calva (14)
- # clj-kondo (23)
- # cljsrn (28)
- # clojars (1)
- # clojure (152)
- # clojure-australia (2)
- # clojure-europe (65)
- # clojure-nl (2)
- # clojure-spec (8)
- # clojure-sweden (3)
- # clojure-uk (45)
- # clojurescript (1)
- # css (12)
- # cursive (16)
- # datomic (9)
- # devcards (2)
- # emacs (1)
- # events (1)
- # graalvm (31)
- # honeysql (10)
- # jackdaw (2)
- # jobs (5)
- # lambdaisland (9)
- # lsp (4)
- # malli (11)
- # meander (43)
- # off-topic (6)
- # pathom (7)
- # polylith (1)
- # portal (14)
- # re-frame (7)
- # releases (1)
- # remote-jobs (1)
- # rewrite-clj (6)
- # shadow-cljs (101)
- # specter (1)
- # tools-deps (26)
- # vim (9)
- # xtdb (2)
in datomic cloud it seems retractions without value work [:db/retract <eid> :some/attr]
to retract any current value(s)… I was surprised by this as the tx data reference documentation doesn’t mention this possibility
It was added more than a year ago in https://docs.datomic.com/cloud/releases.html#616-8879. Could be valuable to update the documentation page.
Hi there. We are currently setting up datomic on-prem to use. And one thing that is not entirely clear is: How do you handle datomic-pro in the CI? We have several CI tasks, that run a lot through the day (depending on the number of pushes). Downloading datomic-pro with the same credentials every time is surely not a good practice, or is it?
Is this for peers or the transactor? less specific advice: CIs often provide a file caching mechanism. E.g. CircleCI restore_cache
and save_cache
we don’t really need a transactor in any of our CI processes, so this may just be a non-problem?