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 bumpCreated with
brew bump-formula-pr.release notes
Fixes #483
Removed extra bats test
Copy of feat(import): validate primary keys early dolthub/dolt#9349
Fixes: #8853
On sql-server restart
__dolt_local_user__is dropped if persistentIf the
__dolt_local_user__is persistent on restart it's logged with a warning and droppedFixes: #9374
Add support for MYSQL_USER/MYSQL_PASSWORD environment variables
Fixes: #483
Local/remote refs take priority in Do What I Mean (DWIM) scenarios where
dolthas to interpret ambiguous input incheckout.If a table and tracking branch share the same name, but local does not exist an error will occur.
--can now be used to clear up ambiguity.case 1:
dolt checkout <ref> -- [<tables>]<ref>must be a singular valid tree, everything else after '--' must be a table.case 2:
dolt checkout -- [<tables>]This is case 1 but without
<ref>.case 3:
git checkout <something> [--](a) If is a commit switch to branch.
(b) If isn’t a commit, and either "--" is present or isn’t a table, no -t or -b is given, and there’s a tracking branch named on exactly one remote (or on the specified remote), then this acts as shorthand to fork local from that remote-tracking branch.
(c) Otherwise, if "--" is present, treat it like case 1.
(d) Otherwise, if a ref treat it like case 1. If a table treat like case 2. If neither fail.
case 4:
git checkout <something> <tables>The first argument must not be ambiguous. If a
<ref>follow case 1, if a table follow case 2. Otherwise, fail.Part 2 of #7623
Migrates
dolt stashcli command to usedolt_stashstored proceduredolt_history_dolt_schemasanddolt_diff_dolt_schemasFixes: #9360
NOTE: currently this is just checking primary keys, but the related issue also mentioned in #1083 references issues with number of args. I'm wondering if I should split that into two separate PRs, or if it's fine to do both - currently I only have the PK validation in place? Personally I would argue to separate them since they are slightly different, albeit similar. But happy to take either path.
Add early validation to check if specified primary keys exist in the import file's schema before processing rows. This prevents users from waiting for large files to be processed only to discover that their primary key column names are invalid.
Changes:
The validation only runs for create operations when primary keys are explicitly specified and no schema file is provided. This ensures fast failure while maintaining backward compatibility.
Before: Users waited minutes for large files to process before seeing "provided primary key not found" errors
After: Users get immediate feedback with helpful column suggestions
Closes: #1083
Needed for doltgres, to put generated system tables in pg_catalog tables.
go-mysql-server
This PR adds a missed edge case from this: fix default value for non null enum columns dolthub/go-mysql-server#2985
We were incorrectly making nullable enum columns take the first value.
MySQL backticks any column names within a check expression preventing any parser errors when round tripping tables, so we should do the same.
fixes: Check constraint with column named
orderbreaks inserts, updates, other operations dolthub/dolt#9343hash.HashOf()inHashLookupsThe incorrect schema was used in the
hash.HashOf()function.n.Schema()is the schema of the entire JoinNode; we just needed the schema of the key.'Test bump: https://github.com/dolthub/ld/pull/20634
UPDATE JOINModified UpdateJoin to be able to apply foreign key constraints
Part of dolthub/dolt#9356
REGEXWe should be able to avoid recompiling the regex if the pattern and flags are static.
Addresses: REGEXP performance regression dolthub/dolt#9366
Other reasons for potential slowness:
drop trigger ...when trigger is invalidWe should ignore parser errors when trying to drop triggers that are invalid.
fixes: Error when trying to drop trigger dolthub/dolt#9359
sql.HashOf()collation awareThis PR adds type/collation information to
HashOf.Additionally, it refactors
HashOfto avoid import cycles and hasgroupingKeyuse the function.fix for:
IN (SUBQUERY)expressions ignore collation dolthub/dolt#9049doltgres fix: [no-release-notes] bump and fix dolthub/doltgresql#1548
Closed Issues
dolt_history_dolt_schemasanddolt_diff_dolt_schemasdolt mergeorderbreaks inserts, updates, other operations__dolt_local_user__account on startupIN (SUBQUERY)expressions ignore collationdolt reset --harddoes not resetdolt_schemasView the full release notes at https://github.com/dolthub/dolt/releases/tag/v1.55.3.