[sverhagen]

Inspired by... but admittedly off-topic... I had recently been wondering how people keep a full auditable history of their data. I've used Hibernate Envers in the past or the now seemingly-defunct Temporal Tables extension for PostgreSQL. What are people using these days? Is DoltLab it, or are there more common solutions?

[cgio]

Can’t say what people are using but keen to hear from others. I am looking into this atm, no implementation yet, and some of the things I am reading about are (I’ll add dolt to this list)

Xtdb: https://xtdb.com/

Terminus: https://github.com/terminusdb/terminusdb

Nessie: https://projectnessie.org/

Dvc : https://dvc.org

Liquid base: https://liquibase.org/

Datasette: https://datasette.io/

Still framing in my mind how schema evolution, x-temporal and e.g. scd in data modelling, version control etc. tie in together in an approach.

[sverhagen]

Not what I was looking for, but a nice list. Just want to call out, what I've also seen in the article that a sibling comment pointed to: if you're gonna mention Liquibase, why would you not mention Flyway: https://flywaydb.org/

Good luck with your search.

[cgio]

No specific reason other than not having come across it. Will add it on my list.

[richardbarosky]

They wrote a blog about database versioning solutions a little while back, which distinguishes schema vs. data versioning tools. I can't say for sure how comprehensive it is, but presumbly it touches on the more well known solutions.

https://www.dolthub.com/blog/2021-09-17-database-version-con...

[parentheses]

I'm surprised you didn't include things like `dat`[0]

[0] https://github.com/dat-ecosystem-archive/dat