Thanks to Datomic's incredible indelible property, I have written many forensic analysis functions roughly like this: • Query the history database for the transactions affecting a specific entity of interest. • Iterate over the tx values constructing an as-of database and then pulling the entity of interest. Here's an example function:

(defn token-history
  [{conn :datomic/connection :as system} token-id]
  (let [db (d/db conn)
        h (d/history db)
        txs (map first (d/q {:query '{:find [?tx]
                                      :in [$ $h ?token-id]
                                      :where [[?t-eid :st.oauth.token/id ?token-id]
                                              [$h ?t-eid _ _ ?tx]]}
                             :args [db h token-id]}))]
    (sequence (map (fn [tx] (let [db (d/as-of db tx)]
                              (d/pull db {:selector [:st.oauth.token/status
                                                     :st.oauth.token/expires-at
                                                     :st.oauth.token/refresh-attempts
                                                     {:st.oauth.token/updated-by [:db/txInstant]}]
                                          :eid [:st.oauth.token/id token-id]}))))
              (sort txs))))

I am working with bigdec's and want to adhere to the advice https://docs.datomic.com/cloud/schema/schema-reference.html: > Consistent results in query depend on the scale matching for all BigDecimal comparisons. You are strongly encouraged to use a consistent scale per attribute. Let's say I have :order/price that I want to have a scale of 10 and :order/qty that should have a scale of 15. The two approaches that come to mind are • Wrap transact in a way that allows me to coerce particular bigdec values to particular scales according to the attribute • Be disciplined at the places in my code where I'm introducing the values and make sure to set the scale there, and enforce this with :db.attr/preds on the attribute schema I'm curious what people's general preferences are relating to these types of transformations and if there's any I'm missing? Are there any helper libraries or functions floating around to deal with such transformations/coercion?