dolt 1.32.2

[BrewTestBot]

Created by brew bump

---

Created with brew bump-formula-pr.

Details

release notes

# Merged PRs
dolt

7373: add dolt rebase command

Adds the dolt rebase command which is supported by the dolt_rebase() procedure.

Related: https://github.com/dolthub/ld/pull/16323

go-mysql-server

2286: Earlier LOAD DATA and insert validation

re: Move validation for InsertInto nodes into the analyzer's validation phase dolthub/go-mysql-server#2283

fixes: sql server panic when uploading table dolthub/dolt#7313
2207: Fix partial left join update when columns have default values or join table is in where clause

I ran into an issue where I was getting a panic when in update queries using left joins with at least some rows being null. The cases where I could confirm this happens is when the query planner wraps the JoinNode in Project or Filter or both. The logic that is supposed to skip null rows for update fails to skip when the node is not directly a JoinNode. I don't know if there are other node types that should be handled the same way in the toJoinNode function I added. This fix resolved the issues I was having.

Side note:

Another related issue I ran into while working on the tests for this was the same type of error happening when the join table is backed by IndexedTableAccess. It seems to set the root join filter to true, with a nested node that has the actual filter. The true filter causes the update skip logic to allow updates on every attempted join, even when null. This was happening for a bit but it stopped while I was messing with the test data so I couldn't keep diagnosing it.

vitess

305: Allow UNIQUE and PRIMARY KEY to be specified on the same column

Related to: id serial primary key SQL created by Drizzle in MySQL mode. Dolt can't execute. dolthub/dolt#7395
302: Detect if a system variable scope was explicitly specified or not

Changes the VarScope function so that it returns whether a scope was explicitly specified, or if one has been inferred.

This is needed because some tooling (e.g. the official MySQL .NET Connector library) will query system variables (e.g. SELECT @@max_allowed_packet) and then will look up the returned value in the result set using the expected column name (@@max_allowed_packet). Currently, from the way we parse the system variable, this was always returned with the scope present, but to match MySQL's behavior, the column name needs to match the requested name.

Related GMS PR: Field response packets MySQL consistency improvements dolthub/go-mysql-server#2266

Closed Issues

7313: sql server panic when uploading table

[github-actions]

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