Dolt's First Stable Production Release

The world's first and only version controlled SQL database is ready for your production workloads. If you've been waiting to try Dolt for it to be stable, fast and compatible, now is the time to try it.

Dolt 1.0 means four things:

1. Forward Storage Compatibility
2. Production Performance
3. MySQL Compatibility
4. Stable Version Control Interface

Read more about it in our release blog

Merged PRs

dolt

• 5882: Apply column defaults when merging in new columns
  Currently, when merging in a new column and updating existing rows for the new column, any column default value for the new column is ignored. This can result in inconsistent data that customers do not expect (e.g. #4456).
  This PR adds initial support for applying column defaults when merging in a new column. Only literal default values are supported in this PR. Supporting column references and function references will require more work to properly resolve those references through the analyzer's code. If an unsupported column default value is present, this change detects that we cannot apply it and errors out the merge, instead of dropping the default value and leaving the new column null.
  Fixes #4456 (which specifically only needs support for literal default values)

go-mysql-server

• 1751: Unions finalize subquery expressions
  The SUBQUERY -> UNION -> SUBQUERY_EXPR pattern was subject to an edge case where the outer SUBQUERY disabled recursively finalizing the inner SUBQUERY_EXPR. The intervening UNION node blocked the outer reach, but failed to re-enable finalizeSubquery during finalizeUnion. This PR edits the finalizeUnionSelector to explicitly re-enable finalize nested subqueries.
  This PR also touches hoistOutOfScopeFilters for the same edge case.
  Issue: #5875
• 1744: Adding tests for altering keyless tables
  Added tests to cover basic keyless table column alterations, to test Dolt change in #5867

Closed Issues

• 5888: sql-server has no way to dynamically set the log level.
• 4456: Default Value not applied to existing rows during merge of schema changes

Latency