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

DoltLite: A SQLite fork with Git-style version control, built with 2k agent PRs

dolthub.com

Post reply on HN
Print view View original

11–20 of 65 posts

Re: DoltLite: A SQLite fork with Git-style version control, built with 2k agent PRs

#11

Post by IanCal »

WatchDog wrote: post #5

So the main feature of this project is that it's easy to fork a database, however it's 1.2x to 4x slower than sqlite, and it's level of testing and validation will be nothing like sqlite. The simple way to fork a sqlite db is just to copy it, but if that is too slow you could use it with a copy on write filesystem, either something native, a FUSE filesystem, or build a sqlite VFS. That would probably be faster to bui…

> however it's 1.2x to 4x slower than sqlite

No? Where are you getting those figures? It feels like you may have pulled that from the 125 and 400 us numbers?

> The simple way to fork a sqlite db is just to copy it, but if that is too slow you could use it with a copy on write filesystem, either something native, a FUSE filesystem, or build a sqlite VFS.

That wouldn’t really solve what dolt does though.

> and it's level of testing and validation will be nothing like sqlite.

They’re using the other dolt tests as well as the SQLite tests. Nothing will hit the level of real world testing SQLite does.

Re: DoltLite: A SQLite fork with Git-style version control, built with 2k agent PRs

#14

Post by WatchDog »

IanCal wrote: post #11
WatchDog wrote: post #5

So the main feature of this project is that it's easy to fork a database, however it's 1.2x to 4x slower than sqlite, and it's level of testing and validation will be nothing like sqlite. The simple way to fork a sqlite db is just to copy it, but if that is too slow you could use it with a copy on write filesystem, either something native, a FUSE filesystem, or build a sqlite VFS. That would probably be faster to bui…

> however it's 1.2x to 4x slower than sqlite No? Where are you getting those figures? It feels like you may have pulled that from the 125 and 400 us numbers? > The simple way to fork a sqlite db is just to copy it, but if that is too slow you could use it with a copy on write filesystem, either something native, a FUSE filesystem, or build a sqlite VFS. That wouldn’t really solve what dolt does though. > and it's lev…

> Where are you getting those figures?

https://www.dolthub.com/blog/2026-06-08-how-fast-is-doltlite...

Re: DoltLite: A SQLite fork with Git-style version control, built with 2k agent PRs

#15

Post by Skinney »

dekelpilli wrote: post #9
vrighter wrote: post #6

Why would I trust my data to a vibe coded database, over a battle tested, tested to hell and back one?

Dolt has been around for 7 years[0]. Doltlite, like most software nowadays, has been touched by LLMs, but dismissing this project as "vibe coded" seems harsh [0] - https://www.dolthub.com/blog/2019-10-14-dolt-a-simple-exampl...

> Doltlite, like most software nowadays, has been touched by LLMs, but dismissing this project as "vibe coded" seems harsh

From the article, at the end of the second paragraph:

> Could a team of agents pull it off? It only took about 2,000 pull requests but DoltLite going Beta proves a team of agents certainly could.

The first PR was merged March 17th.

"vibe coded" seems pretty fitting

Re: DoltLite: A SQLite fork with Git-style version control, built with 2k agent PRs

#16

Post by bawolff »

IanCal wrote: post #12
bawolff wrote: post #7

I don't understand why you would want this.

A version controlled db? Have a look at dolts main page then, it’s been around for some time - this is just adding an embedded version.

I read it, and i think i understand even less than when i started.

Re: DoltLite: A SQLite fork with Git-style version control, built with 2k agent PRs

#17

Post by gunalx »

WatchDog wrote: post #14
IanCal wrote: post #11

Earlier quoted context omitted.

> however it's 1.2x to 4x slower than sqlite No? Where are you getting those figures? It feels like you may have pulled that from the 125 and 400 us numbers? > The simple way to fork a sqlite db is just to copy it, but if that is too slow you could use it with a copy on write filesystem, either something native, a FUSE filesystem, or build a sqlite VFS. That wouldn’t really solve what dolt does though. > and it's lev…

> Where are you getting those figures? https://www.dolthub.com/blog/2026-06-08-how-fast-is-doltlite...

God that had a lot of llm'isms. Couldnt get through it with all the repeats and info bloat.

Re: DoltLite: A SQLite fork with Git-style version control, built with 2k agent PRs

#18

Post by asaddhamani »

dekelpilli wrote: post #9
vrighter wrote: post #6

Why would I trust my data to a vibe coded database, over a battle tested, tested to hell and back one?

Dolt has been around for 7 years[0]. Doltlite, like most software nowadays, has been touched by LLMs, but dismissing this project as "vibe coded" seems harsh [0] - https://www.dolthub.com/blog/2019-10-14-dolt-a-simple-exampl...

It is vibe coded.

But worse.

> Gas Town is for “write-only code”, … If you adopt Gas Town, you will lose the speed benefit of multiple agents if you read the code it produces. The first time you stare at an 8,500 line Git diff and try and parse what happened, you’ve lost. Go back to a single Claude Code session. Gas Town isn’t for you.

So none of the code has even been read by the author, it’s purposely overly verbose. “Touched by LLMs” seems to downplay just how vibe coded this is. I won’t use this database for anything.

Re: DoltLite: A SQLite fork with Git-style version control, built with 2k agent PRs

#19

Post by throw234259 »

vrighter wrote: post #6

Why would I trust my data to a vibe coded database, over a battle tested, tested to hell and back one?

Look at dev process (i did), this think is "tested to hell" and "battle tested".

But the feedback loop was automated and accelerated. Instead of 1000 loops spread over 20 years, it had 1000 loops over a few months.

Calling it "vibe coded" just shows something about you, not the project. It is not production ready yet, but that is not for fast ai dev or for technical reasons. It needs independent reviews, independent verification, and reputation.

Re: DoltLite: A SQLite fork with Git-style version control, built with 2k agent PRs

#20

Post by ncruces »

WatchDog wrote: post #5

So the main feature of this project is that it's easy to fork a database, however it's 1.2x to 4x slower than sqlite, and it's level of testing and validation will be nothing like sqlite. The simple way to fork a sqlite db is just to copy it, but if that is too slow you could use it with a copy on write filesystem, either something native, a FUSE filesystem, or build a sqlite VFS. That would probably be faster to bui…

It's easy to do a VFS that handles instant forking (snapshots).

Here's an in-memory one I made (pretty useful for unit tests): https://github.com/ncruces/go-sqlite3/tree/main/vfs/mvcc

The problem DoltLite solves is merging, not forking.

Post reply on HN