I have a data modelling/querying question. I want to store a heartbeat that a client sends every hour. Datomic recommends using noHistory for things like counters, which makes sense, but I also want to use the heartbeat for billing, i.e. I bill you based on number of heartbeats per month as a proxy of usage. Is it possible to build that query with the tx log even if I have history turned off for an attribute?

if I filter a db to contain only datoms of a certain partition is that a performance win or not?

stijn, the filter would still have to consider all datoms that your datalog looks at, so i’m thinking no

@robert-stuttaford: that’s what I thought as well

@max: the tx log will contain everything that happened, so you could use it for no-history changes. just be aware that reading from the log doesn’t take advantage of any peer caching