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
interface{}instead of alwaysstringThe variable defined for the YAML Marshaller to write user variables to was defined as a
map[string]string, which caused all variables to be read as a string even when they weren't quoted. Changing it to amap[string]interface{}fixes that.fixes: Can't set a numeric session variable using
user_session_varssection of config.yaml dolthub/dolt#8672use errors.New to replace fmt.Errorf with no parameters
We previously would flush stats when an active server detected schema changes, but the same problem affects initializing a server's stats after offline table alters. The prototype here uses tags to persist schema hashes so that we detect differences between stored and present table changes.
Additional improvements to debug logging and error handling. Fixes a separate bug related to re-initializing database statistics after a drop within the same server lifetime.
Note: There are interruption points in-between detecting schema changes, deleting the schema tags, and deleting the data off disk. There is also an interruption point between writing a schema tag and writing the associated data. I've tried structuring the orderings so that the worst-case scenario is we have to do repeated stats collection work:
So an interrupted delete will continue to delete after the process is picked up. And an interrupted write will be missed and have to be recollected.
dolt_diff_<tbl>This PR fixes the panic when attempting to view a diff on a table with virtual generated columns by just skipping over the values.
Ideally, we'd be able to resolve the generated column values themselves and show the diff, but that is not near at hand.
Fixes: Panic on dolt_diff_* with generated column dolthub/dolt#8665
caching_sha2_passworduse withmysqlclientAdded link to blog post with more info on the removal of
mysql_native_passwordauthentication in MySQL-9.0 and how to use Dolt's new support forcaching_sha2_passwordauthentication.Increase the supported stored procedure length from 1K to 8K.
go-mysql-server
Previously if an error was expected but none was produced the test would pass.
ENUMs toTEXTforCASEandCONVERTstatementsfixes: enum conversion type has unexpected results dolthub/dolt#8598
caching_sha2_passwordauthThis change enables users configured with the
caching_sha2_passwordauth plugin to authenticate to a running SQL server. The default authentication plugin is stillmysql_native_password, but users can opt-in tocaching_sha2_passwordby creating a user and explicitly specifying the auth plugin.Note that the
caching_sha2_passwordauth plugin requires running the SQL server with a certificate so that TLS connections can be established.Depends on: Minor bug fixes for
caching_sha2_passwordauth logic dolthub/vitess#390Related to: Support
caching_sha2_passwordauthentication method dolthub/dolt#8496Closed Issues
user_session_varssection of config.yamlcaching_sha2_passwordauthentication methodselect * from dolt_proceduresfor repo used in dolt docs