Dolt is Git for Data: a SQL database that you can fork, clone, branch, merge
1–10 of 185 posts
Re: Dolt is Git for Data: a SQL database that you can fork, clone, branch, merge
#2Re: Dolt is Git for Data: a SQL database that you can fork, clone, branch, merge
#3Is it for versions of the database design or versions of the data?
Re: Dolt is Git for Data: a SQL database that you can fork, clone, branch, merge
#4It’s a bit slower, but smart use of partial/shallow clones can address performance degradation on large repositories over time. You just need to take care of the transformation between “physical” trees/blobs and “logical” objects in your dataset (which may not have 1:1 mapping, as having physical layer more granular reduces likelihood of merge conflicts).
I’m also following Pijul, which seems very promising in regards to versioning data—I believe they might introduce primitives allowing to operate on changes in actual data structures rather than between lines in files, like with Git.
Add to that sound theory of patches, and that’s a definite win over Git (or Doit for that matter, which seems to be same old Git but for SQL).
Re: Dolt is Git for Data: a SQL database that you can fork, clone, branch, merge
#5Re: Dolt is Git for Data: a SQL database that you can fork, clone, branch, merge
#6Problematic name, could become a millstone on the neck of the developer far into the future.
Re: Dolt is Git for Data: a SQL database that you can fork, clone, branch, merge
#7Problematic name, could become a millstone on the neck of the developer far into the future.
Re: Dolt is Git for Data: a SQL database that you can fork, clone, branch, merge
#8Re: Dolt is Git for Data: a SQL database that you can fork, clone, branch, merge
#9Re: Dolt is Git for Data: a SQL database that you can fork, clone, branch, merge
#10Is it for versions of the database design or versions of the data?
(I haven’t used it; I just read the blog.)