Merged PRs
dolt
- 2159: pprof-server usage message on start
I always forget how to connect to the pprof server so I've added a message that comes up when you run dolt with the --pprof-server flag. - 2154: Rebase the database on transaction start
This fixes #2092
As part of this work, also cleaned up manifest reading and writing code. We now always read the manifest flexibly (any known version), and always write the most recent version. - 2152: Fix update on web issue
BulkImportIEA and BulkImportTEA only support Commit, and not Rollback. Dolt uses these for import operations which do not get an explicit Commit or Rollback call. When used on the web for the in memory implementation Commit is used, and should not error. - 2148: no panic if HOME does not exist
#2147 - 2137: Made SQL commits involving a dolt commit atomic
- 2105: merge rows on
dolt table import -u
when import data only represents a subset of the columns
Prior to this fix running this:would result in:dolt sql <1pk5col-ints-sch.sql echo -e 'pk,c1\n1,1\n2,6'|dolt table import -u test echo -e 'pk,c2\n1,2\n2,7'|dolt table import -u test echo -e 'pk,c3,c4,c5\n1,3,4,5\n2,8,9,10'|dolt table import -u test dolt sql -r csv -q 'SELECT * FROM test'
Now it results in:pk,c1,c2,c3,c4,c5 1,,,3,4,5 2,,,8,9,10
pk,c1,c2,c3,c4,c5 1,1,2,3,4,5 2,6,7,8,9,10
go-mysql-server
- 554: Added locks, todo to mutable session state
- 553: Wrote proper number conversion logic
Previously we were relying on thecast
library, which had a few issues with how we expect SQL numbers to function. One such issue was how number strings were handled (such as interpreting"01000"
as a binary number rather than in decimal). There have been more issues in the past that have gone undocumented, but this should fix them (or allow for an easy fix since it's all custom logic now).