timsehn

7 ms·

1.
by timsehn 15d ago
After about three weeks I hand drove three agents in parallel for 8-10 hours/day. There is very little automation.
2.
by timsehn 15d ago
For DoltLite in particular, push/pull/clone/fetch are an elegant solution to the local-first sync problem. You can use data conflicts instead of CRDTs. https://www.dolthub.com/blog/2026-04-27-why-doltlite
3.
by timsehn 26d ago
I'm the CEO of a company that's focused on version control for structured data ie. SQL tables and JSON documents. We share the "version control for everything" vision and think an agentic world needs it. https:/&#x
4.
by timsehn 1mo ago
I’m the author of the linked Prolly Tree article and I launched a prolly tree visualizer last week. Conveniently: https://www.prollytree.com
5.
by timsehn 5mo ago
Thanks for being an early adopter. We learned a lot trying to support your use case and you’re still customers so it can’t have been too bad…
6.
by timsehn 6mo ago
https://docs.dolthub.com/other/faq#why-is-it-called-dolt-are...
7.
Coding Agent Bake Off: Which Is Best?(dolthub.com)
2 points by timsehn 1y ago|0 comments
8.
by timsehn 1y ago
We actually wrote another blog about this because I had the same question. I am the CEO of DoltHub so I can have my engineers write stuff to explain it to me :-) https://www.dolthub.com/blog/2025-06-26-prolly-tree-balan
9.
by timsehn 2y ago
We built a MySQL-compatible one and are building a Postgres-compatible one :-) Free and open source. https://github.com/dolthub/dolt We use the reset functionality to speed up our tests. https://www.dolthub.
10.
by timsehn 2y ago
https://docs.dolthub.com/other/faq#why-is-it-called-dolt-are...
11.
by timsehn 2y ago
Coming soon we'll have the ability to replicate a branch HEAD to MySQL as well.
12.
by timsehn 2y ago
Version Control is not the type of thing "mainstream DBs would adopt". We needed to build a custom storage engine to make querying and diffing work at scale: https://docs.dolthub.com/architecture/storage-engin
13.
by timsehn 2y ago
Most direct users of go-mysql-server use it to test Golang <> MySQL interactions without needing a running server. We here at DoltHub use it to provide SQL to Dolt.
14.
by timsehn 2y ago
> Why is Dolt MySQL flavored? TLDR; Because go-mysql-server existed. https://www.dolthub.com/blog/2022-03-28-have-postgres-want-d... We have a Postgres version of Dolt in the works called Doltgres. https:/&#x2
15.
by timsehn 3y ago
You can do this with a setting: https://docs.dolthub.com/sql-reference/version-control/dolt-...
16.
by timsehn 3y ago
So you can do local first with the `dolt_clone()`, `dolt_remote()`,`dolt_fetch()`, `dolt_pull()`, and `dolt_push()` procedures: https://docs.dolthub.com/sql-reference/version-control/dolt-... as well as the `dolt_
17.
by timsehn 3y ago
Queries on DoltHub need to go to S3 to fetch all the chunks. This only works for databases < 1GB generally. You will get much better performance if you clone the database locally.
18.
by timsehn 3y ago
The insurance database (transparency in coverage) is here (also open data): https://www.dolthub.com/repositories/dolthub/transparency-in...
19.
by timsehn 3y ago
If you clone the database locally it will work. It takes a long time to clone though.
20.
by timsehn 3y ago
If you are just looking for data versioning there is Dolt: https://github.com/dolthub/dolt And that has a user-friendly UI in DoltHub: https://www.dolthub.com/ You wouldn't store the images themse
21.
by timsehn 4y ago
Founder of DoltHub here. One of my team pointed me at this thread. Congrats on the launch. Great to see more folks tackling the data versioning problem. Dolt hasn't come up here yet, probably because we're focused on OLTP use case
22.
by timsehn 4y ago
This is just a database of hospital price URLs. If you want actual prices we have that as well but it's from the beginning of the year: https://www.dolthub.com/repositories/dolthub/hospital-price-...
23.
by timsehn 4y ago
Posted this in our Discord :-)
24.
by timsehn 4y ago
Creator of Dolt here. Thanks for the mention! My cofounder is writing a blog on Monday about how to run Dolt embedded like SQLite. Glad to see more people exploring the space.
25.
by timsehn 4y ago
Creator here. It's slower. This is `sysbench` Dolt vs MySQL. https://docs.dolthub.com/sql-reference/benchmarks/latency We've dedicated this year to performance with a storage engine rewrite. We'll h
26.
by timsehn 4y ago
Creator here. You only connect with a MySQL-client. There is no MySQL code in it. Here's the story if you're curious. https://www.dolthub.com/blog/2022-03-28-have-postgres-want-d... We will eventually build a
27.
by timsehn 4y ago
We're trying to close the performance gap. Current performance on sysbench can be found here: https://docs.dolthub.com/sql-reference/benchmarks/latency We're even slower on heavy transactional use cases.
28.
by timsehn 4y ago
Creator here... Only need Oracle clients but we will eventually have a Postgres foreign data wrapper for the storage engine. I explain how we ended up MySQL in this blog post if you're curious. https://www.dolthub.com/b
29.
by timsehn 4y ago
Creator here... We are a fork of Noms. Lots of incremental changes and we're in the process of a major storage engine overhaul (what we use Noms for) for performance as we speak.
30.
by timsehn 4y ago
One of the creators here... Indeed. Intentional. https://docs.dolthub.com/other/faq#why-is-it-called-dolt-are...

More ›