3 ms·
Perhaps I missed it while skimming, but one thing that’s not really explained is Datasette’s take on versioning. If you edit some rows in a table and change you
by skybrian 3y ago
Perhaps I missed it while skimming, but one thing that’s not really explained is Datasette’s take on versioning. If you edit some rows in a table and change your mind later, is there an undo for just that change?
For small amounts of data, sharing files on GitHub is a default choice and I wonder what I’d be giving up. (There is also DoltHub but it didn’t quite do what I wanted when I kicked the tires a bit.)
DoltHub is explicitly trying to be a “GitHub for data” and it seems like Datasette could become that, though maybe with a different take on versions.
- simonw 3y agoI've been thinking about this quite a bit recently. I want to start adding features where LLMS can help with data cleanup, but for that to be useful it will need VERY robust "undo" for if they make mistakes. I wrote up one of my explorations here: sqlite-history https://simonwillison.net/2023/Apr/15/sqlite-history/ https://simonwillison.net/2023/Apr/15/sqlite-history/ I've also had a lot of success using GitHub itself for versioned data. If your data is less than a GB (and each file is under 50MB) you can dump it out to a GitHub repo and use that to track changes over time. One example of that is my personal blog, here: https://github.com/simonw/simonwillisonblog-backup/tree/main/simonwillisonblog https://github.com/simonw/simonwillisonblog-backup/tree/main... That's using this tool: https://datasette.io/tools/sqlite-diffable https://datasette.io/tools/sqlite-diffable I imagine Datasette Cloud will end up with some sort of hybrid of those approaches.