Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Created by
brew bumpCreated with
brew bump-formula-pr.release notes
1.50.0 introduced a perf regression which mainly effects taking backups to AWS or GCS. This is a partial fix which makes backups perform as before when they are going to a completely new destination. Incremental backups to an existing store are still slower. We continue to work on addressing the regression.
The following query caused a panic in Doltgres, because
DoltTablewas usingTypeCompatibilityCheckerto test if the column type change was compatible.TypeCompatibilityCheckerwasn't able to handle theExtendedTypeinstance and panic'ed. This change makesTypeCompatibilityCheckerignore extended types, since it doesn't know enough about them to determine if a type change is compatible or not.Bumps golang.org/x/net from 0.23.0 to 0.36.0.
updated-dependencies:
hashicorp/go-uuiddependencyWe are already using
github.com/google/uuidfor UUIDs. This dependency was accidentally introduced.hashicorp/go-uuiddependencyWe are already using
github.com/google/uuidfor UUIDs. I think this dependency was accidentally introduced.https://github.com/dolthub/dolt/blob/b7c0ddb4aac3702114c4e060651007d590a8be8c/go/go.mod#L24
https://github.com/dolthub/dolt/blob/b7c0ddb4aac3702114c4e060651007d590a8be8c/go/go.mod#L71
INSERT ... ON DUPLICATE UPDATEwithdolt_docstableAdds a test for the bug fix in Bug fix: Call
StatementBeginfor all TableEditors used ininsertIterdolthub/go-mysql-server#2892Bumps golang.org/x/net from 0.23.0 to 0.36.0.
Commits
85d1d54go.mod: update golang.org/x dependenciescde1ddaproxy, http/httpproxy: do not mismatch IPv6 zone ids against hostsfe7f039publicsuffix: spruce up code gen and speed up PublicSuffix459513dinternal/http3: move more common stream processing to genericConnaad0180http2: fix flakiness from t.Log when GOOS=jsb73e574http2: don't log expected errors from writing invalid trailers5f45c77internal/http3: make read-data tests usable for server handlers43c2540http2, internal/httpcommon: reject userinfo in :authority1d78a08http2, internal/httpcommon: factor out server header logic for h2/h30d7dc54quic: add Conn.ConnectionState[](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores) Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting `@dependabot rebase`. [//]: # (dependabot-automerge-start) [//]: # (dependabot-automerge-end) ---
Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot show ignore conditions` will show all of the ignore conditions of the specified dependency - `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself) You can disable automated security fix PRs for this repo from the [Security Alerts page](https://github.com/dolthub/dolt/network/alerts).
This is a new built-in function added in the go1.21 standard library, which can make the code more concise and easy to read.
go-mysql-server
When building plan nodes to handle altering a column's nullability or type, without respecifying the full column definition, the built node should ensure any column default expressions are resolved.
This originally showed up as a panic in Doltgres, because Doltgres'
TypeSanitzerfound theUnresolvedColumnDefaultinstance and tried to invoke operations on it.Note that it's not currently possible to trigger this issue with Dolt or GMS because MySQL has a more limited syntax than Postgres for altering a column without respecfiying its full column definition, and Dolt/GMS does not support that syntax currently (e.g.
ALTER TABLE t ALTER COLUMN SET VISIBLE).StatementBeginfor all TableEditors used ininsertIterinsertItercan be given asql.RowInserterand asql.RowUpdater, and when theON DUPLICATE UPDATEclause is present, it can use both to update a table.StatementBeginwas only being called on thesql.RowInserterand not for thesql.RowUpdater, which caused a problem for some implementations (e.g.docsWriter) that depend onStatementBeginbeing called.Test for this added to the Dolt package (Test for
INSERT ... ON DUPLICATE UPDATEwithdolt_docstable dolthub/dolt#8988), using thedocWriterimplementation where this bug was originally discovered.Table aliases on update statements break triggers, because we are unable to find any trigger matches on the alias.
The fix is to find the real table name when searching for triggers.
fixes: BUG: BEFORE UPDATE Trigger Not Working in Dolt dolthub/dolt#8926
DROP TABLESWhen multiple tables are supplied to
DROP TABLES, MySQL (and also Postgres) will sort the tables by foreign key dependencies, so that the tables can be dropped cleanly.Resolves
DROP TABLEshould sort tables by dependencies dolthub/doltgresql#1272The rule
eraseProjectionerases the projection fromselect '', which causesvalidateSchemaSourceto error.Adding a case in
validateSchemaSourceresulted in dummy rows being outputted, so I think this is the best solution for now.fixes: Can't
select ''dolthub/dolt#8977This PR introduces a new method for the ExtendedType interface and uses it to allow converting between compatible column types during a foreign key check.
When JSON_LENGTH is passed a JSON object, it should always return the number of fields in the object. However, due to a typo, it currently only returns
1for objects. This PR corrects that behavior.last_insert_iddiscrepancyApparently the
last_insert_idin ok result, is not the same asselect last_insert_id().When there is an auto_increment column, the insert_id in the OKResult is the first value that increments the auto_increment value.
Reverts some changes from: fix insert id dolthub/go-mysql-server#2616
fixes: MySQL is not consistent regarding
last_insert_id;go-mysql-serverceased to emulate this inconsistency in v0.19.0 dolthub/dolt#8914Closed Issues
max_connectionsis reacheddolt gcwarningdolt table import -uinserts and updates duplicate keys instead of failing. Unclear what the desired behavior is.dolt pullfrom DoltHub does not complete (gets stuck) in hours when a clone takes minutesdolt cloneloads all dolt databases in working directory into memorydoltcli commands take a long time for large databasesdolt diff -r sqlanddolt patch