This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2017-03-21
Channels
- # beginners (38)
- # boot (88)
- # cljs-dev (142)
- # cljsrn (2)
- # clojars (1)
- # clojure (107)
- # clojure-berlin (2)
- # clojure-italy (8)
- # clojure-russia (76)
- # clojure-spec (325)
- # clojure-taiwan (3)
- # clojure-uk (28)
- # clojurescript (80)
- # clojurewest (2)
- # core-async (36)
- # core-logic (1)
- # cursive (21)
- # datomic (16)
- # dirac (18)
- # docs (2)
- # emacs (1)
- # euroclojure (3)
- # garden (3)
- # gsoc (2)
- # hoplon (3)
- # immutant (4)
- # jobs-discuss (16)
- # lein-figwheel (5)
- # liberator (17)
- # lumo (19)
- # off-topic (2)
- # om (20)
- # onyx (28)
- # pedestal (50)
- # planck (4)
- # re-frame (5)
- # reagent (3)
- # ring-swagger (13)
- # spacemacs (1)
- # specter (43)
- # testing (3)
- # timbre (3)
- # uncomplicate (1)
- # vim (2)
- # yada (4)
@fenton Sometimes I find it easier to read e.g enums like {:reject/reason :reject.reason/unknown-user}
@yonatanel ok sounds good.
Another reason might be aliases, where you still have the context of the keyword but it isn't disturbing, like ::s/invalid
instead of :clojure.spec/invalid
@fenton can make refactors easier too
i didn't follow this advice and used :min
and :max
for a lot of different things
i had some bugs that i could only fix by going back and being careful about exactly what this was a min/max of
e.g. some needed to be strings and some needed to be numbers, which was screwing up my sorting in places
namespacing would have made the causes of the bugs a lot more obvious, or avoided them
Say, if I have a set #{:a :b :c}
, is there an easy way to find entities that have a :cardinality/many
attribute :e/attr
that contain exactly those values?
…or do I need to query for the attributes and construct my own set outside of the query?
could you simply use an (= #{:a :b :c} ?attr)
expression in a where
clause? (i haven't tried this)
Hmm, I’ll try that. But I suspect that in the where clause I’m only looking at a single attribute value at a time, eg it would be checking for :a
, then :b
, then :c
Sorry, didn't see this. I wound up approaching the problem in a different way that worked, so I didn't get around to trying it.
does anyone have experience running a high throughput transactor? specifically regarding memory settings and increasing from the recommended prod settings?