Havent tried, but I think you could take the last example from https://docs.datomic.com/on-prem/getting-started/see-historic-data.html and add '?tx true' to the last where clause. Sort by tx and all but the first are updates.

Ah sorry, didnt read your question we'll enough.

You could use datoms with the aevt index for this. Scanning all values evt's. Not sure if there is a quicker way.

(->> (d/q '[:find ?v ?tx
            :in $ ?e
            :where
            [?e :session/start-time ?v ?tx true]]
          (d/history db)
          eid)
     (sort-by second)
     (drop 1))

For one specific entity

Actually, since Datomic always retracts the old value before writing a new one you can do this:

(d/q '[:find ?v2 ?tx
       :where
       [?e :session/start-time ?v2 ?tx true]
       [?e :session/start-time ?va ?tx false]]
     (d/history db))

There are 26 more occurrences in the https://docs.datomic.com/cloud/analytics/analytics-other.html section's pages also, for a total of 46 across both sections.

With that said, I guess (or I know) you're hard at work preparing the next release of Datomic Cloud, and that's way more important than updating these docs - I'd say this is true at least until you eventually release a backup-restore solution; but still, let's see this as a signal that we spend a bit of time uselessly investigating the differences between Presto and Trino because of this. 🙂

The release in use now (348) is from the trino fork, but before they renamed it to trino. I’m not sure there’s a not-confusing way to explain this 🙂 Witness my confusion last year: https://clojurians.slack.com/archives/C03RZMDSH/p1655476628432899

Yeah, I read that last week when I was making my way through the docs. 🙂 Your reply helped me make sense right now of this, though, so thanks a lot!

This here seems to be legacy information, not updated with the newish info (I can confirm once I try it; the good values should be easy to find).

This would also seem to be outdated info.

Hi @U0514DPR7 Thanks! We intentionally left it as presto because that is the name of the version (348) we are using (right before the name switch). The name switch happened after we released Analytics and we have not returned to see about upgrading to a newer version from Trino. Your points stand and I will work with the team to see what we can do to make this clearer.