JHjhoechtl·Dec 28, 2020Submission
3 points · Open discussiondolthub
dolt
Go2019–2026
dolthub / dolt
dolt
Dolt – Git for Data
42Distinct people
76Mentions
0Explicit recommenders
24.9KGitHub stars
What to know before exploring
What it is
Dolt – Git for Data
GitHub
Where it is used
No documented product use was verified in the last source check.
What people are saying
No recommendation phrase was found in the indexed comments.
No classified warning is attached to this page. Read the discussions before treating silence as approval.
Also in these discussions
- attic-labs/noms · linked in 3 of the same discussions
- mgramin/awesome-db-tools · linked in 2 of the same discussions
Mentioned in the same Hacker News threads. That is not proof they are substitutes.
This week on Hacker News
Nov 8–Nov 15 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/15/2026, 12:45:45 PM UTC.
No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.
Mentions over time
HN mentions by year76 dated mentions
Observed mentions: 2019-08-06 22:43:54 UTC to 2026-04-14 23:55:55 UTC.
* An incomplete calendar period is marked with an outlined bar. Its count is not directly comparable with a full period.
Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.
View mention counts and date ranges
| Period | Start (UTC) | End (exclusive, UTC) | Mentions | Submissions | Comments |
|---|---|---|---|---|---|
| 2019 | 2019-01-01 00:00:00 UTC | 2020-01-01 00:00:00 UTC | 6 | 2 | 4 |
| 2020 | 2020-01-01 00:00:00 UTC | 2021-01-01 00:00:00 UTC | 19 | 2 | 17 |
| 2021 | 2021-01-01 00:00:00 UTC | 2022-01-01 00:00:00 UTC | 14 | 4 | 10 |
| 2022 | 2022-01-01 00:00:00 UTC | 2023-01-01 00:00:00 UTC | 7 | 2 | 5 |
| 2023 | 2023-01-01 00:00:00 UTC | 2024-01-01 00:00:00 UTC | 12 | 0 | 12 |
| 2024 | 2024-01-01 00:00:00 UTC | 2025-01-01 00:00:00 UTC | 12 | 2 | 10 |
| 2025 | 2025-01-01 00:00:00 UTC | 2026-01-01 00:00:00 UTC | 3 | 0 | 3 |
| 2026 (partial) | 2026-01-01 00:00:00 UTC | 2027-01-01 00:00:00 UTC | 3 | 1 | 2 |
What Hacker News says
19 sourcesDolthub | Los Angeles, CA | Full Time | REMOTE (ONSITE WHEN SAFE)| Full-Stack Engineers
Dolthub is a Series A startup ($7m raised) building git for data. Our core project is an open source database called dolt (https://github.com/dolthub/dolt) that allows git like version control for databases (branches and merges). Dolthub (https://www.dolthub.com/) is built on top of the Dolt datastore and is seeking to build a datahub that allows opensource data collaboration at scale.
We are looking for mid to senior level devs who are passionate about scaling Dolthub and making it the defacto platform for data collaboration. Some work may include getting datasets on to Dolt via ETL/Airflow jobs or even working on the core Dolt DB technology. Our team is filled with rockstar distinguished/senior engineers from places like Amazon, Snapchat, and Google.
Read the rest
You will learn a lot.
Stack: Go, Node.js, Next.js, React.js
See full jd here: https://www.linkedin.com/jobs/view/2166939708/?refId=4890099...
Questions: Reply to this thread or shoot an email to oscar@dolthub.com
Unfortunately, we cannot sponsor H1Bs or F-1 OPT candidates.
Hi all! We wrote a blog about a new feature we released on DoltHub - merging pull requests on the web. Similar to GitHub, users can open a pull request with proposed changes to a Dolt (https://github.com/liquidata-inc/dolt) repository and merge in those changes after review and approval. This is our first step to making it easier to edit data on DoltHub, and we're very excited about the road ahead!
In Merging database changes on the web using DoltHubNoms has gone pretty quiet since the acquisition. Dolt is based on noms (not sure how much is has diverged) and much more active: https://github.com/liquidata-inc/dolt
In The database I wish I hadDolt (https://github.com/liquidata-inc/dolt) and DoltHub (https://dolthub.com) are Git and GitHub for data. This blog discusses our newest feature - first-party accounts and signing in with a username and password.
In Username and Password Login on DoltHubThere aren't many places where Splitgraph intersects with Dolt. Dolt aims to build a database from the ground up to have Git semantics and a real commit graph, whereas Splitgraph works on top of an existing RDBMS (PostgreSQL) and performs its operations by manipulating database tables. Here's a quick overview of differences where we do intersect.
With data versioning, we cherry-picked (no pun intended!) only a few concepts/commands from Git that we think are applicable. In particular,
like Tim mentioned, we don't support cell-level merges. However, we offer a higher level DSL (Splitfiles[-1]) to collaborate on data.
After a Splitgraph image is checked-out, it's just a set of ordinary tables, so you get PostgreSQL feature parity and read-write performance out of the box. That means we're compatible with any existing PostgreSQL clients (Da
Read the rest
taGrip, pgcli, pgAdmin, DBeaver...), tools (Metabase, dbt...) and extensions, including those that define custom types (e.g. PostGIS for geospatial data)[0].
We also offer a way of querying Splitgraph images without checking them out[1]. This lets it download required table regions on the fly (IIRC with Dolt, you have to fully clone the whole dataset and all of its history before querying it) and in a lot of cases can be faster than PostgreSQL itself[2]. This is also completely transparent to and compatible with existing clients.
Splitgraph is decentralized and can treat any instance as a remote and push data there, with authorization provided by PostgreSQL, so you can use methods like LDAP/RADIUS/Kerberos to control access. It looks like you can spin up a Dolt remote with [3] but it's not very well documented so I can't comment on it.
Finally, we offer a lot of features beyond data versioning (reproducible dataset builds with provenance tracking, mounting other databases, automatically generated REST API for all datasets on Splitgraph Cloud etc).
When I tried it out a couple of months ago, Dolt's MySQL server didn't work with mysql_fdw. But their MySQL compatibility is progressing at an impressive pace and if it works now, you'll be able to query Dolt datasets directly from Splitgraph (by running sgr mount mysql[4]) and use them in Splitfiles. In the meantime, you can import data from Dolt into Splitgraph by using their dolt-to-pg adapter.
[-1] https://www.splitgraph.com/docs/concepts/splitfiles
[0] https://www.splitgraph.com/product/splitgraph/integrations
[1] https://www.splitgraph.com/docs/large-datasets/layered-query...
[2] https://github.com/splitgraph/splitgraph/blob/master/example...
[3] https://github.com/liquidata-inc/dolt/tree/master/go/utils/r...
[4] https://www.splitgraph.com/docs/ingesting-data/foreign-data-...
I edit a database newsletter – https://dbweekly.com/ – so tend to always have my eyes out for new releases, what's coming along, and what not. And I thought I'd share a few more things that have jumped out at me recently in case anyone's in the mood for spelunking.
1. QuestDB – https://questdb.io/ – is a performance-focused, open-source time-series database that uses SQL. It makes heavy use of SIMD and vectorization for the performance end of things.
2. GridDB - https://griddb.net/en/ - is an in-memory NoSQL time-series database (there's a theme lately with these!) out of Toshiba that was boasting doing 5m writes per second and 60m reads per second on a 20 node cluster recently.
3. MeiliSearch - https://github.com/meilisearch/MeiliSearch – not exactly a database but basically an Elastic-esque search server written in Rust. Seems to have r
Read the rest
eally taken off.
4. Dolt – https://github.com/liquidata-inc/dolt – bills itself as a 'Git for data'. It's relational, speaks SQL, but has version control on everything.
TerminusDB, KVRocks, and ImmuDB also get honorable mentions.
InfoWorld also had an article recently about 9 'offbeat' databases to check out if you want to go even further: https://www.infoworld.com/article/3533410/9-offbeat-database...
Exciting times in the database space!
Dolt (https://github.com/liquidata-inc/dolt) and DoltHub (https://dolthub.com) are Git and GitHub for data. Having a versioned database makes collaborating on data more fluid and reliable in the same way that Git improves source code collaboration for software engineers.
This blog discusses DoltHub’s newest feature, cell history inspection. You can inspect the changes between versions of every cell in every table with just a click, making debugging between versions easy to trace.
In Cell History Inspection on DoltHubAuthor here. I'm a software engineer at Liquidata (https://liquidata.co), the company behind Dolt (https://github.com/liquidata-inc/dolt) and DoltHub (https://dolthub.com). We're building the future of data distribution and collaboration; come check out what we're up to!
I wrote this article as part of a series on the technology behind DoltHub. In this installment, I explore how GraphQL rescued us from a nasty pit of sadness we got stuck in calling our gRPC API directly from our front end.
Hope folks find it interesting. Happy to answer any questions!
In GraphQL Saved Us from the gRPC Dumpster Fire We CreatedHi Hacker News,
CEO of the company that built Dolt (https://github.com/liquidata-inc/dolt) and DoltHub (https://www.dolthub.com) here.
If you aren't Dolt is Git versioning wrapped around a SQL database. DoltHub is a place to share databases in Dolt format. We think it's a better way to share open data on the internet. No importing. SQL comes with the format.
Every month we'll be publishing a blog on new or interesting datasets on DoltHub. This is the first in that series:
https://www.dolthub.com/blog/2020-05-01-april-dataset-spotlight/
If you put a dataset on Dolt and DoltHub you want us to spotlight, hit us up (https://www.dolthub.com/contact).
1 points · Open discussion> So I create a local repo with dolt, and now I want someone else to collaborate on this dataset with me, without using dolthub. How I do this?
The best I could find is utils/remotesrv in the repository [0], which seems to enable collaboration.. but also seems bit basic and it's not clear if https is supported.
[0] https://github.com/liquidata-inc/dolt/tree/master/go/utils/r...
In I Want Decentralized Version Control for Structured DataOP here. I'm a software engineer with Liquidata, creators of Dolt (https://github.com/liquidata-inc/dolt), a version-controlled SQL database with Git semantics, and DoltHub (https://www.dolthub.com/), a home for Dolt repositories on the web. We just released initial support for webhooks on DoltHub, and I wrote the above article on using them with Jenkins to set up basic continuous integration testing for a large COVID-19 dataset (https://www.dolthub.com/repositories/Liquidata/corona-virus) we maintain and regularly update.
Hope you find this interesting, and don't hesitate to ask if you have any questions!
Matt
In Continuous Integration for Data with DoltHub WebhooksYeah, the SQL shell needs some work, including its readline implementation which is kind of broken. Filed an issue for this:
https://github.com/liquidata-inc/dolt/issues/505
In Dolt is Git for dataYep, dolt is a fork of noms:
https://github.com/liquidata-inc/dolt#credits-and-license
(and sorry :( -- yay open source?)
In Dolt is Git for dataSo does git. I know, I know, git doesn't provide the features you expect from a full fledged database, but neither does Dolt.
Dolt even has some content in a GitHub wiki, which uses git as a database backend for a web app: https://github.com/liquidata-inc/dolt/wiki
In Dolt is Git for dataShowing the 15 most recent of 19 sources. Enable JavaScript to search and browse every indexed mention.