hi, just started learning datomic. Is the following picture correct representation of a-usage ?

And this

And this

@wistb That is broadly correct, yes. In addition, both the Transactor and the Peer will communicate with Storage. There isn't really any "transactor" for the in-memory database, it's just the Peer library providing a local version of the d/transact API.

Is there an easy way to see what version of datomic a transactor I'm connecting to is?

(Like, get it out of the connection object, ideally)

are tx ids guaranteed to be sequential, or is that an implementation detail?

It is really hard to imagine a datomic with non sequential tx

Tx is just the t with the tx-partition bits added

yeah, i understand. though, my question still stands 😉

@jeremy Yes, transaction entity IDs increase monotonically over time. The same is true of any entity ID within its partition.

ok, thank you!

how would one go about overriding the print-method for db/ids?

@uwo Call class on a dbid, then defmethod print-method

@uwo you mean for tempids?

yes. I think maybe what I’m looking to do is more along the line of (. clojure.pprint/simple-dispatch addMethod datomic.db.DbId pprint-myrecord)… I may have been mistaken about print-method..?

@favila yes

basically aiming to pretty print some data that has tempids, but I want to keep the tempids in the format that prn would produce

this was my solution

(defn pprint-myrecord [b] (.write *out* (str b)))

(def my-print (. clojure.pprint/simple-dispatch addMethod datomic.db.DbId pprint-myrecord))

(clojure.pprint/with-pprint-dispatch my-print
  (clojure.pprint/pprint
etc..

@jeremy note that the ts don't necessarily increase by one from one transaction to the next.

val_waeselynck: good to know ,thanks