You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
9461: Correctly delete rows from DOLT_CONFLICTS_ tables when the table schema has changed from the base.
The logic for marking conflicts as resolved had an implicit assumption that the table schema had not changed from the ancestor commit. If the schema had changed, then it would compute an incorrect key for the conflicts map, and would fail to remove conflicts.
9459: Add @GLOBAL.dolt_auto_gc_enabled system variable to inspect whether auto GC is enabled.
The system variable is read-only. The only way to enable Auto GC remains setting:
behavior:
auto_gc_behavior:
enable: true
in the config.yaml file which is given to dolt sql-server in its --config parameter.
9446: Flush outputs in archive command. Fixes flaky test
Make lambabats more reliable.
Also, catch an error which was previously ignored.
9441: Only print Query Ok results in interactive shell.
This PR changes the CLI so that we only print the "Query OK" and "Database Changed" messages when using the interactive shell; this matched MySQL behavior.
Additionally, it now caches the output of DDL iterators. This way, we are not dependent on the printing to complete to have the changes committed (rowIter.Close() to be called).
companion pr: dolthub/go-mysql-server#3059
fixes: #9281
go-mysql-server
3070: Don't prune VirtualColumnTable tables
fixes #8968
Pruning columns in VirtualColumnTable tables causes indexing errors when VirtualColumnTable Projections are evaluated
Future work: prune VirtualColumnTable Projections so that VirtualColumnTable underlying table can be pruned
3067: #9427 - Prevent user and system variables in column defaults and generated values
Fixes #9427
Adds validation to prevent user variables (@variable) and system variables (@@variable) from being used in column default value expressions and generated column expressions.
Modified validateColumnDefault function in sql/analyzer/resolve_column_defaults.go to detect UserVar and SystemVar expressions and return ErrColumnDefaultUserVariable error.
Added ErrColumnDefaultUserVariable error definition to sql/errors.go to match MySQL's error message format.
🤖 Generated with Claude Code
3065: Fix enum columns cannot have auto_increment
Fixes #9423
Added ErrInvalidColumnSpecifier error message
Added enum type validation in validateAutoIncrementModify and validateAutoIncrementAdd
Enabled previously skipped test case for enum auto_increment validation
🤖 Generated with Claude Code
3063: Fix count(*) for added generated columns
Fixes #8959
3062: Allow DEFAULT keyword in UPDATE for generated columns (issue #9438)
Fixes #9438
Modified validation in dml.go to allow DEFAULT expressions for generated columns
For generated columns, DEFAULT now correctly uses the generated expression
Maintains existing validation that rejects non-DEFAULT values for generated columns
🤖 Generated with Claude Code
3060: Merge scopeColumn types in SetOp scope
fixes #9024
Previously, the scopeColumn type defaulted to that of the corresponding scopeColumn in the left scope. This would cause a type conversion error if the left scopeColumn was a less general type than the corresponding right scopeColumn.
The merged scopeColumn is also made nullable if one of the merging columns is nullable.
GeneralizeTypes also checks if two types are already equal. This prevents DolgresTypes from always being generalized as a LongText.