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
sql.Schema
for conflicts table schemaPreviously, we would create a new schema of
NomStringKind
for every column. Now, we just reuse the underlying sql.Schema.Failed to write conflicts table dolthub/dolt#7874
Related to Running sql-server from an empty state make inconsistent repository dolthub/dolt#7873
Resolves Confusing error messages when using Dolt CLI from within a running Dolt sql-server directory dolthub/dolt#7875
sql-server
should initialize persisted global varsThe local config store (
.dolt/config.json
) can store persisted global variable values, but when--data-dir
is used when starting asql-server
, the local configuration doesn't get loaded properly.--data-dir
When using the
--data-dir
flag to work on a Dolt directory outside of the current working directory, the local configuration in the Dolt directory wasn't getting correctly loaded. This change evaluates the--data-dir
parameter earlier, so that the first time we load the Dolt environment, we can pass the data directory and get the local configuration loaded correctly.This just adds a function to the
RootValue
for special merge logic, which is used by Doltgres.go-mysql-server
LIKE NULL
edge caseThis PR fixes an edge case where
SELECT <str> LIKE NULL
should returnNULL
instead offalse
.fixes trim whitespace when casting from string dolthub/dolt#7854
VALUES
constructorWhen the number of rows in a
... VALUES ROW(...), ROW(...)
statement were not equal, we would throw a panic.This PR also unskips some tests that are now fixed.
Companion PR: support
INSERT INTO ... (VALUES ROW(...))
statement dolthub/dolt#6849fixes: support
INSERT INTO ... (VALUES ROW(...))
statement dolthub/dolt#6849Slow_queries
,Max_used_connections
,Com_select
, andConnections
Adds support for four new status variables:
Note that
Connections
currently only reports the successful connection attempts, but MySQL includes all connection attempts in that status variable. To capture the failed attempts, we'll need to expose that information from the Vitess layer.Also removes a mutex that was covering the whole scope over all status variables. Now that each individual status variable has a value that uses an
atomic
instance, we don't need to synchronize at a larger scope.Related to Initial support for
show status
dolthub/dolt#7646vitess
add support for statements like:
select cast(<str> as character)
select cast(<str> as double precision)
select cast(<str> as read)
row
optional in VALUES constructor and insert statementThis PR adds additional syntax support for VALUE constructor.
fixes support
INSERT INTO ... (VALUES ROW(...))
statement dolthub/dolt#6849fixes make
ROW
keyword optional inVALUES
statement dolthub/dolt#7853Closed Issues
ROW
keyword optional inVALUES
statementINSERT INTO ... (VALUES ROW(...))
statementdrop database