3 ms·
I actually think git is MUCH better suited to this than a traditional database. I've built track-changes-over-times things in relational databases before and i
by simonw 6y ago
I actually think git is MUCH better suited to this than a traditional database.
I've built track-changes-over-times things in relational databases before and it's a real pain to implement!
I've actually started using a GitHub repository to back up the PostgreSQL database that powers my blog, because it's a really cheap way of getting a revision history of that database without having to write any extra code: https://github.com/simonw/simonwillisonblog-backup/commits/main https://github.com/simonw/simonwillisonblog-backup/commits/m...
- tfigment 6y agoI think you want temporal tables for historical dimensions. Postgres doesnt have good support as its a bolt on. MariaDB has good support for it now.
- baby 6y agoI'm not sure I understand the difficulty, your columns are the fields in your object, the rows are the different points in time