Clojurians Log v2

the numbers are eids, so you can just pull them using d/pull. You could query all attribute names, and use the query-result to map over the 4th entry to make it more efficient. depending your usecase.

On-Prem or cloud?

Both https://docs.datomic.com/on-prem/peer/peer-getting-started.html and https://docs.datomic.com/cloud/dev-local.html have equivalent memory databases which you could create and tear down for every unit-test, no production-code modification required.

is there a way to trace which https://docs.datomic.com/cloud/query/query-data-reference.html#rules) were satisfied during a query execution? i'm working on a rule list that is sometimes flat, sometimes recursive, and i'd like to be able explain which conditions were met (or not) for auditing purposes

I typically add an extra constant binding to each rule

[(ground :rule-impl-1) ?matched-rule-impl]