|
| 1 | +# Created with WinGet Updater using komac v2.12.1 |
| 2 | +# yaml-language-server: $schema=https://aka.ms/winget-manifest.defaultLocale.1.10.0.schema.json |
| 3 | + |
| 4 | +PackageIdentifier: DoltHub.Dolt |
| 5 | +PackageVersion: 1.57.3 |
| 6 | +PackageLocale: en-US |
| 7 | +Publisher: DoltHub |
| 8 | +PublisherUrl: https://github.com/dolthub/dolt |
| 9 | +PublisherSupportUrl: https://github.com/dolthub/dolt/issues |
| 10 | +Author: DoltHub |
| 11 | +PackageName: Dolt |
| 12 | +PackageUrl: https://www.dolthub.com/ |
| 13 | +License: Apache-2.0 |
| 14 | +LicenseUrl: https://github.com/dolthub/dolt/blob/HEAD/LICENSE |
| 15 | +CopyrightUrl: https://raw.githubusercontent.com/dolthub/dolt/master/LICENSE |
| 16 | +ShortDescription: Dolt is a SQL database that you can fork, clone, branch, merge, push and pull just like a git repository. |
| 17 | +Description: |- |
| 18 | + Dolt is a SQL database that you can fork, clone, branch, merge, push and pull just like a git repository. |
| 19 | + Connect to Dolt just like any MySQL database to run queries or update the data using SQL commands. |
| 20 | + Use the command line interface to import CSV files, commit your changes, push them to a remote, or merge your teammate's changes. |
| 21 | +Moniker: dolt |
| 22 | +Tags: |
| 23 | +- cli |
| 24 | +- data |
| 25 | +- git-for-data |
| 26 | +- versioning |
| 27 | +ReleaseNotes: |- |
| 28 | + Merged PRs |
| 29 | + dolt |
| 30 | + - 9587: Bug fix: Update secondary index correctly during a merge with a schema change |
| 31 | + During a merge, Dolt applies diffs to existing indexes to sync their data with the changes being merged in. If the table schema has changed between the merge base and the left/right branches of the merge, Dolt was using the incorrect value tuple to remove the row from the index. This resulted in a customer issue where the secondary index still contained rows and the foreign key validation logic was incorrectly detecting FK violations, even though the child table was empty. |
| 32 | + As a follow-up to this, we need to investigate other similar cases in the secondary index merger and see if other diff types have a similar issue. |
| 33 | + - 9585: Run gofmt and goimports on generated protobuf files to ensure clean diffs |
| 34 | + This change adds gofmt and goimports steps to the protobuf generation process to ensure that generated .pb.go files are consistently formatted. |
| 35 | + - 9577: Remove broken symlink |
| 36 | + - 9574: Fix dolt_preview_merge_conflicts for doltgres |
| 37 | + - 9551: #9530 - Fix auto-increment display for SHOW CREATE TABLE |
| 38 | + Fixes #9530 |
| 39 | + Companion PR: dolthub/go-mysql-server#3103 |
| 40 | + Fixed auto-increment display discrepancy in SHOW CREATE TABLE by adding type checking to prevent incrementing beyond integer type maximums. |
| 41 | + go-mysql-server |
| 42 | + - 3123: Support decimal unique keys |
| 43 | + fixes #3071 |
| 44 | + - 3122: Allow SYSTEM as valid time zone |
| 45 | + - 3119: Add test for setting time zone from table value |
| 46 | + - 3118: Validate time zone before setting it |
| 47 | + fixes #9559 |
| 48 | + - 3116: fix panic in stats histogram union and intersect |
| 49 | + I'm not 100% how to repro this, but there is definitely something up with the Union and Intersect logic in stats histograms. |
| 50 | + Based on the stack trace, there's a panic when attempting to Union histogram buckets. |
| 51 | + It seems like the logic assumes that the histogram keys are always shorter than the number of buckets. |
| 52 | + This PR fixes the Union and Intersect logic to compare the keys without the assumption, and adds some unit tests. |
| 53 | + fixes: #9143 |
| 54 | + - 3114: #9511 - Fix SET type casting to CHAR and BINARY |
| 55 | + Fixes #9511 |
| 56 | + - Added convertSetToStringForStringContext() helper function following existing patterns |
| 57 | + - Modified convertValue() to handle SET types in both CHAR and BINARY conversion cases |
| 58 | + - 3109: #9544 - Fix time type foreign key constraints |
| 59 | + Fixes #9544 |
| 60 | + Allows foreign key constraints to be created between time-related types (DATETIME, TIMESTAMP, TIME) with different precisions or cross-type references, matching MySQL behavior. |
| 61 | + Closed Issues |
| 62 | + - 9590: More granular control over restrictions |
| 63 | + - 9544: time types and foreign keys |
| 64 | + - 9530: auto_increment with max integers does not error properly |
| 65 | + - 9469: Support SET in string context |
| 66 | + - 9511: SET type does not cast correctly to char or binary |
| 67 | + - 9143: index out of range panic on CTE |
| 68 | + - 9559: set time_zone should validate timezone |
| 69 | + - 3071: In-memory tables don't support DECIMAL(...) UNIQUE KEY |
| 70 | +ReleaseNotesUrl: https://github.com/dolthub/dolt/releases/tag/v1.57.3 |
| 71 | +ManifestType: defaultLocale |
| 72 | +ManifestVersion: 1.10.0 |
0 commit comments