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 bump
Created with
brew bump-formula-pr
.release notes
dolt_diff_summary()
Potential fix for Why DOLT_DIFF_SUMMARY shows record without data change and schema change? dolthub/dolt#8907
Previously, diffs would only look at the schema hash when determining whether or not a table had a schema change. However, the auto increment counter, which is considered part of the schema, is not stored in the schema flatbuffer and thus does not affect the schema hash.
This led to situations where a diff would detect that a table had changed (because the table hash changed), but it reported neither a data change or a schema change (because the data hash and schema hash were the same.) This was confusing.
Now,
dolt_diff_summary
will correctly report a schema change when the auto increment counter has changed, anddolt diff
will show the autoincrement value in theSHOW CREATE TABLE
output.Adds the
\pager [on|off]
capability todolt sql
.Fixes: Feature Request: Add pager support for dolt sql terminal output dolthub/dolt#8883
Currently no tests. Would require expect, and is probably beyond the investment in time for this feature.
vet
errors related to non-constant format strings.go-mysql-server
This is the GMS side of an issue to properly display diffs when the autoincrement counter on a table changes.
We add a new interface,
AutoIncrementGetter
for tables that store AutoIncrement info, even if they can't generate autoincremented ids (because they're immutable snapshots of a table with an autoincrement column)vitess
Back ports vitessio/vitess@24820d8
INSERT ... RETURNING
supportPostgres allows
INSERT
statements (and alsoUPDATE
andDELETE
) to specify aRETURNING
clause with select expressions and will then evaluate those expressions against the affected rows and return the results. This change adds initial support for theRETURNING
select expressions so that they can be represented in the AST. (PostgreSQL docs)Closed Issues
last_insert_id
gives 0 when 0 is explicitly specified for anauto_increment
primary key in an insertion