dolt 1.81.1

[BrewTestBot]

Created by brew bump

---

Created with brew bump-formula-pr.

Details

release notes

# Merged PRs
dolt

10347: fixed output bug for foreign key constraints

go-mysql-server

3389: remove convertLeftAndRight

This PR removes c.convertLeftAndRight, which avoids calls to c.Left().Type() and c.Right().Type().

Not entirely sure why receiver methods would impact performance this much, but benchmarks say so.

Benchmarks: test revert compare dolthub/dolt#10342 (comment)
3384: Look at every join node parent when computing outer scopes.

Previously, when building scopes for subqueries that appear inside joins, we would only track a single parent join node. If the subquery had multiple join parents, we would only be able to resolve references to the innermost subquery. This inhibits the optimizations we can perform.

This PR uses a custom tree walker to track a list of parent join nodes, and includes an example of a query that was not previously possible to optimize.
3370: Wrap errgroup.Group.Go() calls for consistent panic recovery

Each spawned goroutine needs a panic recovery handler to prevent an unexpected panic from crashing the entire Go process. This change introduces a helper function that wraps goroutine creation through errgroup.Group and installs a panic recovery handler and updates existing code to use it.

vitess

448: Move SERIAL type out of numeric type definitions so that unsigned value is not overwritten

fixes dolthub/dolt#10345

MySQL docs
446: Added DISTINCT ON expressions

Related PRs:

Added DISTINCT ON handling dolthub/go-mysql-server#3369
Added DISTINCT ON handling dolthub/doltgresql#2181



Closed Issues

10345: SERIAL type alias creates signed BIGINT instead of unsigned
10329: Foreign key constraint doesn't enforce index requirement on receiving table

View the full release notes at https://github.com/dolthub/dolt/releases/tag/v1.81.1.

---

[github-actions]

🤖 An automated task has requested bottles to be published to this PR.

Caution

Please do not push to this PR branch before the bottle commits have been pushed, as this results in a state that is difficult to recover from. If you need to resolve a merge conflict, please use a merge commit. Do not force-push to this PR branch.