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
Fixes broken Github actions based on recently implemented robot checks on the sqlite server.
Fixes dolthub/dolt#9641
Add normalization in CSV string export conversion to detect non-canonical types.
Due to an accidental variable shadowing, error messages that occurred when iterating over query results wouldn't be displayed if the user runs
dolt sql
in interactive mode.Prior behavior:
string
s and[]string
Changes:
Companion PR: cache
sql.Schema
inplan.Project
andplan.TableAlias
dolthub/go-mysql-server#3158Fixes: @@port is hard-coded to 3306 dolthub/dolt#5898
Dolt CI does not support wildcards in branch specs.
fixes dolthub/dolt#9279
relies on dolthub/go-mysql-server#3156
Companion fix is here: Made LOAD DATA handle NULL values and defaults correctly dolthub/go-mysql-server#3155
sql.Row.Append()
Companion PR: avoid using
sql.Row.Append()
dolthub/go-mysql-server#3154go-mysql-server
Previous, as part of computing hashes for MySQL's hash functions (MD5, SHA1, etc), we could convert the input into a text type. But this would cause errors in strict mode of the input was a binary value that was not valid utf8.
By converting the input into a binary type, we keep all the same behavior, except that binary inputs now work correctly.
sql.Schema
inplan.Project
andplan.TableAlias
Changes:
plan.Project.Schema()
andplan.TableAlias.Schema()
create a newsql.Schema
every time they are called, which can be a lot during analysis. So, the results are cached.sql.Index.Expressions()
retrieves a new[]string
, so we should cache that as well. Additionally, many times we unqualify the results,so I added aUnqualifiedExpressions()
to avoid doing this extra processing every time.idxExprsColumns
to avoid usingstrings.Split
to avoid extra allocationspart of dolthub/dolt#9279
relies on dolthub/vitess#424
dolt changes made in dolthub/dolt#9672
sql.Row.Append()
sql.Row.Append()
will always make a deep copy of the row, so we should avoid it.Instead we have copies to cached
sql.Rows
or reuse the backing array throughappend()
(sometimes golang's runtime will allocate a new one anyway).We weren't enforcing any name length constraints on triggers, and when customers created triggers with very long names (i.e. over 64 characters, the MySQL limit), they could encounter problems with table schemas that don't support longer lengths.
In this change, we apply a max trigger name length of 96 characters and reject
CREATE TRIGGER
statements that create triggers with names longer than that limit. We chose 96 characters for the limit, instead of copying MySQL's 64 character limit, so that this change would not break existing applications that are creating trigger names slightly longer than MySQL's 64 character limit.Fixes dolthub/dolt#9641
Fixed Max1Row optimization being incorrectly applied to UNION subqueries. Also fixed UNION schema type reconciliation using GeneralizeTypes().
fixes dolthub/dolt#7095
@@port
,@@hostname
, and other system variablesfixes dolthub/dolt#5898
related to dolthub/dolt#6037
MySQL docs
vitess
This adds parsing and sqlType info for a VECTOR type, matching MySQL's behvaior.
part of dolthub/dolt#9279
Fixes
SELECT ... FOR UPDATE NOWAIT
, introduced in MySQL 8.0, cannot be parsed correctly dolthub/dolt#9604Closed Issues
View the full release notes at https://github.com/dolthub/dolt/releases/tag/v1.58.4.