Ask HN: How do you version your data?

Re:Ask HN: How do you version your data? by clord on Sunday February 19, 2017 @10:13PM (#13683970)

I wrote[0] about a method I've used with success in the past. Essentially you use the previous version's hash as the name for the next version. The benefit is that merging the work of multiple developers is easier. I ran the process manually when I did it and would love to hear if someone writes a script that makes the process easier.

[0]: https://medium.com/@clord/for-migration-of-schemas-use-versi...

[ Parent | on HN ]

Re:Ask HN: How do you version your data? by webmaven on Sunday February 19, 2017 @10:43PM (#13684109)

So, your data versions form a DAG, sort of like Git commits?

[ Parent | on HN ]

Re:Ask HN: How do you version your data? by peclink on Monday February 20, 2017 @02:41AM (#13685254)

What a great idea, thanks for sharing!

BTW, why using shell scripts to write migrations is so unpopular? We have lots of language/framework specific solutions or some «language agnostic» tools using plain SQL, both ways are rather limiting.

[ Parent | on HN ]

Re:Ask HN: How do you version your data? by ComputerGuru on Monday February 20, 2017 @02:53AM (#13685314)

So if you release version 1.0 with hash x, then release version 1.1 with hash y, and then release version 1.0.1 with hash z, 1.0.1 == 1.1?

[ Parent | on HN ]

Re:Ask HN: How do you version your data? by clord on Monday February 20, 2017 @02:13PM (#13690009)

For branching schemas, yes it gets complicated. But at least you get a nice conflict while merging the branches (at the right place) These conflicts help guide a rewrite of the schema history into something consistent. That's part of it: when a merge happens, you basically have to create a new migration that does the merge too.

and if you never merge the forks, there is no problem. they likely won't share a production database anyway, right?

[ Parent | on HN ]

Re:Ask HN: How do you version your data? by setheron on Monday February 20, 2017 @11:20AM (#13688484)

It's like a block chain!

[ Parent | on HN ]