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
This defines a new system table function
DOLT_JSON_DIFF(arg1, arg2)For each difference between the two provided JSON objects, this function produces a row describing the path to the changed value, and the before and after values. It can be used in a lateral join with other system tables to show changes in multiple rows or across multiple commits.
The tests in dolt_json_diff_test.go are go tests for the table function, confirming that it has the same behavior as the unit tests for the underlying differ.
The added engine tests are used to test more complicated behavior, such as using this table function in a lateral join.
require_client_certto sql server configuration optionsAdds a new
require_client_certproperty to thelistenersection of a sql server configuration file. When enabled, clients must present a certificate and must connect over a secure connection. Ifca_certis also provided in the server's configuration, the provided client cert will also be verified against the server's CA cert.Note that this mode prevents
dolt sqlfrom being able to connect to a running Dolt SQL server, sincedolt sqlwill connect to the server but does not have a valid client cert and private key to use.Related to Implement client certificate authentication dolthub/dolt#10008
Doc updates Update config.yaml reference dolthub/docs#2718
go-mysql-server
The schema throughout a groupby query does not change, so we should not be recreating one for the grouping key each time.
Benchmarks: test group schema dolthub/dolt#10119 (comment)
Previously gms relied on the ComInitDB callback to update the processlist with the currently authenticated user. This resulted in the processlist showing "unauthenticated user" for connections which were already authenticated but which had not issued a ComInitDB. Those connections could issue queries which would also appear in the process list. Adding an explicit callback when the authentication is successful and allowing the processlist entry to be Command Sleep with an authenticated user even when no database is selected is more correct behavior here.
Iter.Next(),RowToSQL, andcallbackinto separate threadsThis PR expands on an optimization where we separate
iter.Next()andRowToSQL+callback()into two separate threads. Now,iter.Next(),RowToSQL, andcallback()all run in their own goroutines with corresponding buffered channels communicating between them.Additionally, this PR tidys up the
resultForDefaultIterandresultForValueItercode.Benchmarks: threads bump dolthub/dolt#10103 (comment)
vitess
This allows a server implementation to know the authenticated user without waiting for the first command interactions, such as ComQuery or ComInitDB.
Enables implementations to have access to the connection. Needed as part of mutual TLS auth work so that implementations can validate connection properties. Also matches the interface definitions in the official vitess repo.
Closed Issues
View the full release notes at https://github.com/dolthub/dolt/releases/tag/v1.78.3.