Fork me on GitHub
#datomic
<
2017-03-21
>
yonatanel00:03:58

@fenton Sometimes I find it easier to read e.g enums like {:reject/reason :reject.reason/unknown-user}

fenton00:03:43

@yonatanel ok sounds good.

yonatanel00:03:01

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

thedavidmeister00:03:48

@fenton can make refactors easier too

thedavidmeister00:03:01

i didn't follow this advice and used :min and :max for a lot of different things

thedavidmeister00:03:45

i had some bugs that i could only fix by going back and being careful about exactly what this was a min/max of

thedavidmeister00:03:11

e.g. some needed to be strings and some needed to be numbers, which was screwing up my sorting in places

thedavidmeister00:03:45

namespacing would have made the causes of the bugs a lot more obvious, or avoided them

timgilbert17:03:22

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?

timgilbert17:03:57

…or do I need to query for the attributes and construct my own set outside of the query?

devth17:03:17

could you simply use an (= #{:a :b :c} ?attr) expression in a where clause? (i haven't tried this)

timgilbert17:03:54

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

devth20:03:56

did it work? (curious)

timgilbert20:03:26

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.

djjolicoeur18:03:24

does anyone have experience running a high throughput transactor? specifically regarding memory settings and increasing from the recommended prod settings?