5 ms·
DoltLite: A SQLite fork with Git-style version control, built with 2k agent PRs
- grebc 3mo agoDid I read that correctly that there’s no WAL?
- anon291 3mo agoI let agents do their things but I would not trust them with my data without extensive validation. A database efforts main product is not exotic data structures but validation.
- Joel_Mckay 3mo agoOne of the reasons SQLite was mostly stable over the years was it sand-boxed its closed developer environment, and clearly defined the project scope. While controversial, they did not have to deal with common accountability issues associated with screening anonymous malicious and or incompetent clown PR. =3 https://www.youtube.com/watch?v=T4Upf_B9RLQ https://www.youtube.com/watch?v=T4Upf_B9RLQ
- WatchDog 3mo agoSo 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 build, faster to run, and easier to validate.
- IanCal 3mo ago> 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.
- WatchDog 3mo ago> Where are you getting those figures? https://www.dolthub.com/blog/2026-06-08-how-fast-is-doltlite/ https://www.dolthub.com/blog/2026-06-08-how-fast-is-doltlite...
- gunalx 3mo agoGod that had a lot of llm'isms. Couldnt get through it with all the repeats and info bloat.
- alsetmusic 3mo agoDunno if I'd have directly attributed the writing to LLMs had I not read this, but I wouldn't have opened the link otherwise. Holy crap, that reads just like the documentation / explainers that I have Claude write for future agents or to remind me what I had it do in the future.
- IanCal 3mo agoAh yes so the 4x slower isn’t really a real world case and you’d have to explicitly measure yours - it’s not a fixed slowdown but depends on table size - and it’s for doing many many single inserts in a row, which you’d be batching either way.
- Izkata 3mo agoThat's probably why they gave a range in their original comment.
- IanCal 3mo agoWhich isn’t correct, either for real world cases or worst case linear inserts.
- WatchDog 3mo agoHow is it not correct? Sure the benchmark does not measure a real world application, but I never claimed it was. Do you have a better benchmark to share? I thought I was being charitable by using a benchmark published by the database's own authors.
- ncruces 3mo agoIt'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 https://github.com/ncruces/go-sqlite3/tree/main/vfs/mvcc The problem DoltLite solves is merging, not forking.
- OskarS 3mo ago> The simple way to fork a sqlite db is just to copy it SQLite recommends against doing that [1] while a transaction is active, because the copy might have some pre/post data in it which could potentially cause corruption. Presumably this isn't an issue with copy-on-write filesystems assuming they copy atomically, but I probably still wouldn't do it, instead use the backup API or VACUUM INTO (if nothing else, because VACUUM INTO will also obviously VACUUM the copy). If you're not attached/writing to it, then of course it's fine. [1]: https://www.sqlite.org/howtocorrupt.html#_backup_or_restore_while_a_transaction_is_active https://www.sqlite.org/howtocorrupt.html#_backup_or_restore_...
- nagaiaida 3mo agoif you don't trust something to survive an atomic filesystem snapshot, why would you trust it to survive sudden power loss?
- OskarS 3mo agoThat's what I'm saying, if you have a CoW filesystem, backing up with atomic snapshots is almost certainly fine, SQLite's advice against copying probably doesn't apply to that. But just typing `cp` in a terminal is probably not a good idea if a transaction is active (even if you're on a CoW filesystem, `cp` in experience usually isn't atomic without some flags).
- vrighter 3mo agoWhy would I trust my data to a vibe coded database, over a battle tested, tested to hell and back one?
- dekelpilli 3mo agoDolt 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-example/ https://www.dolthub.com/blog/2019-10-14-dolt-a-simple-exampl...
- Skinney 3mo ago> 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
- solarkraft 3mo agoIf going through a strongly designed process with quality gates is vibe coding, I guess so. I thought the term was reserved fir “claude, make this happen” style development and the term for the more professional approach was “agentic development”, though this seems to be another layer higher. Grouping it all under “vibe coded” loses precision. Sure, it uses AI, but differently from other projects and with different implications.
- bawolff 3mo agoI don't understand why you would want this.
- IanCal 3mo agoA 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.
- bawolff 3mo agoI read it, and i think i understand even less than when i started.
- grebc 3mo agoThey’re probably a VC backed product in search of a solution.
- thesz 3mo agoThere are filesystems (ZFS and btrfs) with snapshots and this feature can be used to version-control things. They both do copy-on-write and this is pretty close to what content-addressable storage would give you in terms of compression.
- SipitenoMK 3mo agoWould be good, but why not to vibe code this database myself if I had a problem with my current database?
- solarkraft 3mo agoYou’d have to do the relevant R&D and maintain the product.
- Sharlin 3mo ago"But Claude does that for me"
- vonnieda 3mo agoPsyched to see this! I've been working on my own similar thing that sucks and I don't want to - I want to write a local first music app that syncs across all my devices. This might get me there!
- joelwallis 3mo agoUnrelated to the post – but if you're trying to build smt that "magically syncs" across devices, you'd like to use CouchDB (and it's front end companion, PouchDB). They solve this problem for you, and it's solved in a very, very reliable way for years! FWIW, search [and research] about offline-first apps. Lots of gems in this niche!
- michelangelo 3mo agoPre 2020 HN reading this would be stoked.
- sureglymop 3mo agoBut post 2020 HN contains 70% AI related posts on the front page such that the moment it is revealed that something is connected to AI, the excitement seems to falter (understandably so).
- nylonstrung 3mo agoEverything touching this ecosystem (Gas Town, Dolt, Beads) seems like the absolute nadir of vibecoded slop This specific community has been a Schelling point for some of the worst engineering practices I've ever seen and a desire to abstract away all details of code to LLM personas like the "Refinery" and "Deacon"
- oreally 3mo agoI'm a little more interested how they automated the process to such a degree. How do they do it? Subagents?
- timsehn 3mo agoAfter about three weeks I hand drove three agents in parallel for 8-10 hours/day. There is very little automation.
- OutOfHere 3mo agoThe biggest limitation I see is the absence of a Go client. I know this opens a can of worms, but using ncruces/wasm2go, or just coordinating with ncruces/go-sqlite3 might work.
- parasxos 3mo ago[dead]
- joelwallis 3mo agoIt's wonderful to see people trying to fork SQLite in any way possible, to supposedly build a better product with AI, out of smt that's been built by seriously talented people for over 20 years. Kudos to the team behind SQLite. These people built smt absolutely amazing!