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
IF NOT EXISTS
and table existsThis PR addresses various issues related to
CREATE TABLE IF NOT EXISTS ...
queries.Before, we simply ignored the table exists error, and continued creating indexes, foreign keys, and checks.
This led to errors when attempting to create indexes/foreign keys/checks that already exists.
Additionally, it would errorneously create indexes/foreng keys/checks that did exist.
The correct behavior is to do nothing if
IF NOT EXISTS
is specified and the table exists.Also this contains some refactors and simplifications.
fixes Conditionally creating a table in a script produces index already exists error dolthub/dolt#7602
We were panicking when attempting to insert/delete tokens that exceed the column type length.
It appears as though MySQL simple ignores these tokens.
fixes: Panic is Wikipedia import cause by a Replace into a table with Full text indexes dolthub/dolt#7593
benchmark stats
When performing range lookups, we convert the key to the type of the column.
The conversion throws an error when the key doesn't fit within the type for the index.
The fix is to promote these (only for StringType) so the ranges fit.
There were issues with
type.Promote()
for all types.Additionally, there are some inconsistencies with MySQL when performing these checks with NUL characters (
\0
). They are skipped tests for now.related Select statement throwing too large for column error dolthub/dolt#7588
json_pretty
MySQL Docs:
https://dev.mysql.com/doc/refman/8.0/en/json-utility-functions.html#function_json-pretty
I can't figure a clean way to get the insert editor's edit accumulator and table editor data in sync when a self-referential foreign key initializes the session editor during analysis. So I just forced us to mutate the edit accumulator's auto increment id, which should prevent bugs of the kind we've been seeing. Zach might have a better understanding of how this should work.
fixes: Self-referencing foreign key constraint breaks auto-incrementing ids in memory mode dolthub/go-mysql-server#2369
vitess
fixes One more issue related to the Adobe Commerce ( Magento ) installation. dolthub/dolt#7601
Adding parsing support for:
This PR adds
binary
as a valid charset option.Additionally, this changes
CHARSET
to expand to synonymCHARACTER SET
for parsing in GMS.fixes
default charset=binary
is messing up in a create table statement dolthub/dolt#7576Closed Issues