Clojurians
#datomic
<
2015-08-01
>

This page is not created by, affiliated with, or supported by Slack Technologies, Inc.

max01:08:12

something really strange is going on

max01:08:25

I have an attribute that has cardinality one, but it has two values

max01:08:29

user=> (d/pull db '[* {:db/cardinality [:db/ident]} {:db/valueType [:db/ident]}] :server/last-heartbeat-at)
{:db/index false, :db/valueType {:db/ident :db.type/instant}, :db/noHistory false, :db/isComponent false, :db/fulltext false, :db/cardinality {:db/ident :db.cardinality/one}, :db/doc "", :db/id 158, :db/ident :server/last-heartbeat-at}
user=> (d/q '[:find ?e ?hb :in $ ?e :where [?e :server/last-heartbeat-at ?hb]] db 17592186962108)
#{[17592186962108 #inst "2015-07-31T23:45:01.167-00:00"] [17592186962108 #inst "2015-08-01T00:45:01.195-00:00"]}
user=>

bkamphaus13:08:35

@max: we’ll follow up with diagnostics, etc. on the support ticket. If this is a high churn attribute (the name leads me to suspect that it is), we have a suspicion about what’s going on. Will confirm before going into it more.

max13:08:57

thanks @bkamphaus

potetm14:08:51

@bkamphaus: I would be very interested in knowing what ya’lls suspicion is, even if it turns out that it isn’t the cause of this issue.

robert-stuttaford15:08:18

@potetm, @bkamphaus ditto