Skip to content

0.55.6

Choose a tag to compare

View all tags
@github-actions github-actions released this 12 Mar 02:15
v0.55.6
77600b3

Merged PRs

doltgresql

  • 2443: Added proper dolt_branch_control functionality
    Fixes:
    • #2435
      This fixes two primary issues with dolt_branch_control. The first is that we'd error when encountering a destination GMS type, as we make the assumption that all GMS types have been handled once we reach a certain point in the analyzer. This is false for Dolt system tables that may be modified, so now cast those types to their closest Doltgres type for analysis.
      The second fix deals with how superusers are handled between Doltgres and GMS. Doltgres uses its own permission model since it's fundamentally different than GMS' model, but dolt_branch_control internally checks for a superuser (or pseudo-superuser) to allow some commands without explicit privileges given. This adds a layer of indirection so that checks for superusers specifically will work as expected.
  • 2439: check for 'check_function_bodies' configuration parameter…
    … when creating functions
    Depends on: dolthub/go-mysql-server#3465
  • 2415: Support text array parameters
    Prisma blocking bug. Right now if you try to bind a query with a text array we scan it incorrectly and error out.
  • 2413: Added additional testing for TIMESTAMP
    This adds testing for TIMESTAMP and TIMESTAMPTZ, which were missing. This also adds a step in CI that changes the locale to the west coast since we already had such assumptions in other tests (that were eventually changed), and there's no other way to test timezones otherwise.
  • 2408: support int2vector and oidvector types
  • 2402: #2373 fix VALUES subquery unwrap from dropping clauses

    Summary

    • Replace overly permissive len(inSelect.From) == 1 guard in nodeAliasedTableExpr with isTrivialSelectStar, which only unwraps bare SELECT * FROM (VALUES ...)
      subqueries with no additional clauses (projections, LIMIT, ORDER BY, DISTINCT, WHERE, GROUP BY, HAVING)
    • Add *plan.Offset guard to TypeSanitizer to prevent OFFSET literals inside subqueries from being converted to Doltgres types, which caused GMS validateOffsetAndLimit
      to reject them with "invalid type: bigint"
    • Un-skip mixed-type VALUES-in-subquery tests and add mixed-type variants plus OFFSET-specific assertions
      Closes: #2373
  • 2384: support privileges for routines and sequences
    Depends on: dolthub/go-mysql-server#3450

Closed Issues

  • 2435: INSERT INTO dolt_branch_control fails with "non-Doltgres type found in destination
  • 2388: Cannot call unnest on pg_index column indoption.
  • 2373: Bug: VALUES inside subquery ignores projections, LIMIT, and ORDER BY
Assets 9
Loading