Merged PRs
dolt
- 9220: Bump undici from 5.28.5 to 5.29.0 in /.github/actions/ses-email-action
Bumps undici from 5.28.5 to 5.29.0.Release notes
Sourced from undici's releases.
v5.29.0
What's Changed
- Fix tests in v5.x for Node 20 by
@mcollinain nodejs/undici#4104 - Removed clients with unrecoverable errors from the Pool nodejs/undici#4088
Full Changelog: nodejs/undici@v5.28.5...v5.29.0
Commits
9528f68Bumped v5.29.0f1d75a4increase timeout for redirect test2d31ed6remove fuzzing tests6b36d49fix redirect test in Node v16648dd8fmore fix for the wpt runner on Windowsa0516badon't use internal header state for cookies (#3295)87ce4affix test/client for node 20c2c8fd5fix: accept v20 SSL specific error for alpn selection in http/282200bd[v6.x] fix wpts on windows (#4093)47546fatest: fix windows wpt (#4050)- Additional commits viewable in compare view
[](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). - Fix tests in v5.x for Node 20 by
- 9219: Adding
dolt_update_column_tag()stored procedure
Adds thedolt_update_column_tag()stored procedure to update a column's tag. This is an advanced operation that most users will not need to use. This blog explains more about column tags and column tag conflicts.
Example usage:Follow ups:CALL dolt_update_column_tag('myTable', 'col1', 4321);
- Add docs for the new
dolt_schema_update_tag()stored procedure - The
dolt schema update-tagCLI command should be updated to use this stored procedure.
- Add docs for the new
go-mysql-server
- 2981: Unwrap wrapper values used in JSON aggregation functions, and un-skip accidentally-skipped tests for this behavior.
We were accidentally skipping most of the tests inTestJsonScripts. An error in the test harness meant that skipping one test in this suite would also skip all additional tests.
A few of the skipped tests were for JSON aggregation functions. The recent "Adaptive Encoding / Wrapper Values" optimization wasn't working properly with these functions because the wrapped values provided to these functions weren't being unwrapped before being inserted into JSON documents. These tests would have caught that issue, but didn't because they were disabled.
This PR fixes the issue and also re-enables the test. - 2980: Unwrap inputs to JSON_OBJECT.
The inputs to the JSON_OBJECT function are expected to be strings for the keys, and the expected types for the values. So we need to check whether the inputs are wrapper values and unwrap them.
The safest thing to do is unwrap the value when the document is created, so this PR does that. In theory, allowed wrapped values to be used as document values and unwrapping them at the use site could improve performance for certain queries that create JSON objects in memory but then only read some of the fields. But that's likely an infrequent enough situation that it's not worth the added complexity. - 2978: Bug fix: ensure an active transaction is set before preparing a query
Also adds support for running transaction tests with prepared statements.
Fixes: #9213