This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2016-08-24
Channels
- # admin-announcements (1)
- # alda (22)
- # aws-lambda (1)
- # beginners (9)
- # boot (17)
- # cider (39)
- # cljs-dev (10)
- # cljsjs (1)
- # cljsrn (14)
- # clojure (88)
- # clojure-android (1)
- # clojure-dev (9)
- # clojure-india (1)
- # clojure-russia (271)
- # clojure-spec (5)
- # clojure-uk (101)
- # clojurescript (74)
- # clojutre (11)
- # component (2)
- # cursive (24)
- # datascript (7)
- # datomic (9)
- # dirac (13)
- # docs (3)
- # emacs (4)
- # garden (21)
- # hoplon (9)
- # jobs-rus (5)
- # lein-figwheel (3)
- # leiningen (13)
- # luminus (12)
- # off-topic (1)
- # om (24)
- # onyx (84)
- # proton (3)
- # re-frame (39)
- # reagent (21)
- # rethinkdb (1)
- # slack-help (10)
- # specter (4)
- # test-check (1)
- # untangled (35)
- # yada (2)
@yonatanel the default expression doesn't seem to support '[* (default :something/a "na")]
. I have to write my function to get all keys, mapping to default value and merge back to current one.
@nxqd: why does that bother you? merging the defaults into the entity returned by datomic can be done succinctly in clojure.
i don't believe so, no, @magnars
@hans yeah, I thought having default expression
would solve the problem cleanly but it doesn't.
@nxqd It is not really unclean to do it the way I suggested. Datomic has a very broad data model and what you're describing is narrow in comparison. If you want to restrict Datomic's open data model to something closer to your application, implementing a layer between your application and Datomic is the right thing to do.