←back to thread

Dolt is Git for Data: a SQL database that you can fork, clone, branch, merge

(github.com)
752 points crazypython | 1 comments | 06 Mar 21 21:15 UTC | HN request time: 0.206s | source
Show context
bitslayer ◴[06 Mar 21 21:23 UTC] No.26370635[source]▶
Is it for versions of the database design or versions of the data?
replies(2): >>26370639 #>>26370870 #
skybrian ◴[06 Mar 21 21:54 UTC] No.26370870[source]▶
Both. Schema changes are versioned like everything else. But depending on what the change is, it might make merges difficult.

(I haven’t used it; I just read the blog.)

replies(1): >>26372168 #
fiedzia ◴[07 Mar 21 01:15 UTC] No.26372168[source]▶
BTW. I wish all databases versioned their schema and kept full history. This should be a standard feature.
replies(1): >>26372555 #
codesnik ◴[07 Mar 21 02:23 UTC] No.26372555[source]▶
keep history just as a changelog to see when and what was changed? or something with versions you actively can revert to? I suppose one of the problems is that changing schema is usually interleaved with some sorts of data migrations and conversion and those I have no idea how to track without using some general scripting language, like migrations in many frameworks which are already there.
replies(1): >>26375118 #
1. fiedzia ◴[07 Mar 21 11:46 UTC] No.26375118[source]▶
Just storing a changelog would be very useful. I could for example compare db version some app was developed for with current state. Most companies will store schema migrations in git, but doing anything with this information is difficult. Having this in db would make automated checks easier.