This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2019-06-19
Channels
- # announcements (2)
- # beginners (448)
- # calva (10)
- # cider (27)
- # clojure (121)
- # clojure-argentina (2)
- # clojure-brasil (6)
- # clojure-chicago (1)
- # clojure-colombia (9)
- # clojure-ecuador (1)
- # clojure-europe (1)
- # clojure-italy (14)
- # clojure-mexico (1)
- # clojure-nl (19)
- # clojure-spec (11)
- # clojure-uk (160)
- # clojurescript (25)
- # core-async (7)
- # cursive (8)
- # data-science (1)
- # datascript (1)
- # datomic (4)
- # devops (2)
- # graalvm (3)
- # hoplon (1)
- # immutant (1)
- # jackdaw (32)
- # jobs (2)
- # joker (2)
- # keechma (9)
- # leiningen (26)
- # luminus (13)
- # off-topic (2)
- # overtone (2)
- # quil (5)
- # reagent (38)
- # reitit (13)
- # shadow-cljs (16)
- # spacemacs (2)
- # tools-deps (4)
- # xtdb (12)
With datomic's "the database as a value" approach, do you treat your functions as "pure"? (defn some-query [db args....]
and pass the db
everywhere?
taking this into account of course: https://docs.datomic.com/cloud/best.html#consistent-db-value-for-unit-of-work
@lockdown- Yeah, it also makes testing a breeze once you dynamically create and destroy databases.
👍 4
@lockdown- it also makes the use of libs like scope-capture super useful since you can interact with it using the REPL even after a test/http request has run