github dolthub/dolt v1.8.0
1.8.0

latest releases: v1.43.0, v1.42.20, v1.42.19...
14 months ago

This release contains backwards incompatible changes:

  • The dolt_merge() procedure now is able to merge with a dirty working set if no conflicts will occur. This differs from the previous behavior which would always fail a merge if there are any uncommitted changes in the working set.

Per Dolt’s versioning policy, this is a minor version bump because users of dolt_merge() results will need to be aware of this new behavior.

Merged PRs

dolt

  • 6360: Slightly better copy in README opening
  • 6352: Bug fix: Encode binary values in hex for SQL patch statements
    Current SQL formatting code converts binary values to strings, which won't round-trip back to the database correctly. This PR changes binary values to be hex-encoded.
    Fixes #6350
  • 6346: Allow empty databases in the shell prompt
    Easy to reproduce issue:
    mkdir foobar
    cd foobar
    dolt sql-server
    
    dolt sql
    > select 1;
    
    And panic() follows. This actually happens for any command, so create database dba included.
  • 6344: updates dolt_merge to allow dirty working sets with no conflicts
    Currently, the dolt_merge stored procedure doesn't allow any uncommitted changes in the working set, it will abort the merge if any are found. However the CLI (and git) allows uncommitted changes in the working set if they won't get stomped by the merge. This change updates the dolt_merge stored procedure to allow that.

Closed Issues

  • 6350: dolt patch generates invalid statement for tables with varbinary keys
  • 6322: Incorrect DECIMAL precision
  • 6319: dolt gives constraint violation on merge when one doesn't exist

What's Changed

  • Slightly better copy in README opening by @timsehn in #6360
  • Bug fix: Encode binary values in hex for SQL patch statements by @fulghum in #6352
  • [no-release-notes] /go/performance/continuous_integration/SysbenchDockerfile: change distro from buster to bullseye by @coffeegoddd in #6361
  • updates dolt_merge to allow dirty working sets with no conflicts by @stephkyou in #6344
  • Allow empty databases in the shell prompt by @macneale4 in #6346

Full Changelog: v1.7.6...v1.8.0

Latency

Read Tests MySQL Dolt Multiple
covering_index_scan 2.03 3.02 1.5
groupby_scan 12.98 17.95 1.4
index_join 1.3 4.82 3.7
index_join_scan 1.23 2.3 1.9
index_scan 32.53 58.92 1.8
oltp_point_select 0.14 0.47 3.4
oltp_read_only 2.71 8.13 3.0
select_random_points 0.31 0.8 2.6
select_random_ranges 0.37 1.14 3.1
table_scan 33.12 58.92 1.8
types_table_scan 74.46 170.48 2.3
reads_mean_multiplier 2.4
Write Tests MySQL Dolt Multiple
bulk_insert 0.001 0.001 1.0
oltp_delete_insert 6.32 6.43 1.0
oltp_insert 2.76 3.19 1.2
oltp_read_write 6.55 15.83 2.4
oltp_update_index 3.02 3.19 1.1
oltp_update_non_index 2.81 3.19 1.1
oltp_write_only 3.96 7.84 2.0
types_delete_insert 5.47 7.04 1.3
writes_mean_multiplier 1.4
Overall Mean Multiple 2.0

Don't miss a new dolt release

NewReleases is sending notifications on new releases.