Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

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

github.com

Post reply on HN
Print view View original

11–20 of 185 posts

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

#13

Post by rapnie »

ademarre wrote: post #7
Klwohu wrote: post #5

Problematic name, could become a millstone on the neck of the developer far into the future.

Agreed. I couldn't immediately see if it was "DOLT" or "do it", as in "just do it". It's the former.

I was going back and forth between the two until seeing doLt in terminal font.

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

#15

Post by jrumbut »

It's amazing this isn't a standard feature. The database world seems to have focused on large, high volume, globally distributed databases. Presumably you would't version clickstream or IoT sensor data.

Features like this that are only feasible below a certain scale are underdeveloped and I think there's opportunity there.

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

#16

Post by chub500 »

justincormack wrote: post #9

I collected all the git for data open source projects I could find a few months back, there have been a bunch of interesting approaches https://docs.google.com/spreadsheets/d/1jGQY_wjj7dYVne6toyzm...

I've had a fairly long-term side project working on git for chronological data (data is a cause and effect DAG), know of anybody doing that?

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

#18

Post by laurent92 »

Wordpress would have benefited from this.

What a lot of webmasters want is, test the site locally, then merge it back. A lot of people turned to Jekyll or Hugo for the very reason that it can be checked into git, and git is reliable. A static website can’t get hacked, whereas anyone who has been burnt with Wordpress security fail knows they’d prefer a static site.

And even more: People would like to pass the new website from the designer to the customer to managers — Wordpress might have not needed to develop their approval workflows (permission schemes, draft/preview/publish) if they had had a forkable database.

Post reply on HN