I actually think git is MUCH better suited to this than a traditional database. ... | Hacker News

Hacker Newsnew | past | comments | ask | show | jobs | submit

simonw on Oct 9, 2020 | parent | context | favorite | on: Git scraping: track changes over time by scraping ...

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/m...

tfigment on Oct 9, 2020 | [–]

I 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 on Oct 10, 2020 | [–]

I'm not sure I understand the difficulty, your columns are the fields in your object, the rows are the different points in time

Consider applying for YC's Fall 2026 batch! Applications are open till July 27.
Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact