This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2017-01-07
Channels
- # aws (2)
- # bangalore-clj (4)
- # beginners (62)
- # boot (74)
- # cider (408)
- # cljsrn (17)
- # clojure (117)
- # clojure-dusseldorf (1)
- # clojure-russia (21)
- # clojure-spec (17)
- # clojure-uk (15)
- # clojurescript (154)
- # cursive (3)
- # datomic (16)
- # emacs (33)
- # funcool (3)
- # hoplon (99)
- # off-topic (7)
- # om (10)
- # overtone (3)
- # portland-or (1)
- # protorepl (9)
- # re-frame (83)
- # reagent (11)
- # remote-jobs (1)
- # ring-swagger (24)
- # specter (10)
- # untangled (1)
- # yada (11)
❓ if I have a denormalized value, and then piece of query, what’s the best way to trim the value? e.g. value: [:rows [{:name “one” :id 1}{:name “two” :id 2},,]
and the query is [:name]
, meaning I need for every row grab only the name and drop everything else
@ag the Om Next queries are basically datomic matches. I think reading a bit on that topic may illuminate the structure and syntax. http://docs.datomic.com/query.html Scroll down to the queries that have a where
clause.
:where*
in many om.next examples, I see alot of @state
inside defmethod read :some/key
. I worry that I get inconsistent total query result because each :some/key read deref the global state
@mavbozo I don't understand your concern, since JS is single threaded
@ag (map #(select-keys % query) data)
?
Is there a way to get tempids reconciliation for remote reads with the default reconciler merge functions?