zachmu

50 ms·

241.
by zachmu 6y ago
Yes. It's public now, just incomplete.
242.
by zachmu 6y ago
We're running a $10,000 bounty to assemble this information into a queryable database: https://www.dolthub.com/repositories/dolthub/hospital-price-... You get paid based on the percentage of rows you contribu
243.
by zachmu 6y ago
Great question. Check out this blog post about use cases written by our founder and CEO. https://www.dolthub.com/blog/2020-03-30-dolt-use-cases/ I've forwarded your bug report to our web team.
244.
by zachmu 6y ago
Postgres support is planned, but we're concentrating on supporting MySQL 100% first. Paying customers who wanted this might make us change the priority order.
245.
Implementing join planning in our open source Golang SQL query engine(dolthub.com)
105 points by zachmu 6y ago|15 comments
246.
by zachmu 6y ago
No, that's not possible. A panic must be recovered in the goroutine in which it occurs. An unrecovered panic in any goroutine kills the entire process, not just the offending goroutine. There is no way to top-down wrap an entire go p
247.
Implementing pushdown to optimize joins in our open source Golang SQL engine(dolthub.com)
2 points by zachmu 6y ago|0 comments
248.
Implementing triggers in our open-source Golang database(dolthub.com)
1 points by zachmu 6y ago|0 comments
249.
Our startup chose Discord over Slack for customer chat(dolthub.com)
4 points by zachmu 6y ago|0 comments
250.
by zachmu 6y ago
Hey, thanks for the kudos! FWIW we are absolutely working on modes of using the product that "just work" like a normal database without any explicit commits / merges. In that case commits would happen automatically (maybe one
251.
by zachmu 6y ago
We're building a very literal "git for data" product, Dolt. (doltdb.com). I'm very curious about this criticism: > Git semantics, ("branche", "merge", "commit") are not well suited for da
252.
by zachmu 6y ago
Dolt actually addresses this need exactly. You can query tables at two different revisions without checking out the two different branches. E.g.: `SELECT * FROM S AS OF '2fabbg';` `SELECT * FROM W AS OF '4c4490';` (Branc
253.
by zachmu 6y ago
You can do historical queries two different ways: 1) `SELECT * FROM state_populations AS OF 'master'` to get the repo as it existed at a particular timestamp / ref name 2) `SELECT * FROM dolt_diff_state_populations WHERE ...`
254.
by zachmu 6y ago
Depends what you mean by "work" and "large," I guess. We have repos in the 250 GB range that definitely push the limits of functionality, but everything still works (pull, push, merge, clone, etc., and queries return the
255.
by zachmu 6y ago
> you caan get most of the useful git-like time-travel semantics (modulo schema migrations) out of timeseries data with a separate transaction history table Well, not really. Dolt isn't just time travel. If all you want is time trav
256.
How and why we rewrote our SQL engine's integration tests with harnesses(dolthub.com)
3 points by zachmu 6y ago|0 comments
257.
Reverse-engineering JetBrains DataGrip to work with our open-source SQL server(dolthub.com)
4 points by zachmu 6y ago|0 comments
258.
We are adopting go-MySQL-server, SQL execution engine that powers Dolt(dolthub.com)
6 points by zachmu 6y ago|0 comments
259.
by zachmu 6y ago
One of the cool things about Dolt is that you can query the diff between two commits. This functionality is available through special system tables. You specify two commits in the WHERE clause, and the query only returns the rows that chang
260.
by zachmu 7y ago
Blog author here. This post discusses how we use our git for data product, Dolt, to store test results, and how this lets us use SQL queries to analyze test regressions on our 6M+ test query dataset. Example: dolt_sql_performance> se
261.
Using “Git for data” to find and analyze test regressions(dolthub.com)
9 points by zachmu 7y ago|3 comments
262.
by zachmu 7y ago
Blog author here. This is a 4/20 themed round up of marijuana datasets and interesting queries on them. Highlights: * Why are there no pictures of weed in ImageNet? * Cannabis testing in Washington state * Connecticut medical marijuana
263.
Roundup of marijuana data sets in honor of 420(dolthub.com)
7 points by zachmu 7y ago|1 comments
264.
by zachmu 7y ago
You can rebase to change the history. As with git, if you do this, everyone with a clone will need to clone a fresh copy, as they can no longer merge with the remote HEAD.
265.
by zachmu 7y ago
Yeah, 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
266.
by zachmu 7y ago
This is the result of a simulation of a COVID-19 outbreak in the US Congress under a variety of experimental conditions: https://www.dolthub.com/blog/2020-03-27-whos-at-risk-of-covi... Black X's represent losses o
267.
Simulated Losses to a Covid-19 Outbreak in the US Congress(dolthub.com)
8 points by zachmu 7y ago|1 comments
268.
by zachmu 7y ago
This blog post discusses our implementation of the AS OF clause for our custom open-source SQL database, Dolt! In addition to the usual timestamp semantics, Dolt databases can be queried using git-like refs. Examples: SELECT * FROM myTable
269.
Implementing AS OF clauses with Git refs (HEAD~) in our open-source database(dolthub.com)
4 points by zachmu 7y ago|1 comments
270.
by zachmu 7y ago
Have you heard of Dolt? It's git for data. https://github.com/liquidata-inc/dolt

More ›