Skip to content

1.41.4

Compare
Choose a tag to compare
@github-actions github-actions released this 11 Jul 23:58

Merged PRs

dolt

  • 8107: Optimize JSON_SET and JSON_REPLACE on IndexedJsonDocument
    This PR includes a new implementation of the JSON_SET and JSON_REPLACE functions that leverage the new indexed JSON storage format.
    For JSON documents that span multiple chunks, only the affected chunks need to be loaded and modified, allowing operations to scale with the size of the removed value instead of the size of the entire document.
  • 8103: Optimize JSON_REMOVE on IndexedJsonDocument
    This PR includes a new implementation of the JSON_REMOVE function that leverages the new indexed JSON storage format.
    For JSON documents that span multiple chunks, only the affected chunks need to be loaded and modified, allowing operations to scale with the size of the removed value instead of the size of the entire document.

go-mysql-server

  • 2591: Bug fix: Fix @@binlog_row_metadata, add @@binlog_row_image
    Fixes an error in the definition for the @@binlog_row_metadata system variable that prevented it from being queried. Adds the @@binlog_row_image system variable that was missing.
  • 2590: Fix databases iter for information_schema tables
    Doltgres information_schema tables include the schemas for the current database, not all databases
  • 2588: Only register version function if it doesn't already exist
  • 2587: Fix information_schema catalog and schema names
    We had already made this change for doltgres here, this just applies it to more information_schema tables
  • 2580: Remove a duplicate column from information_schema
    Just what it says on the tin. This duplicate column causes problems for DuckDB when attempting to connect to doltdb databases.
  • 2578: Catch panics in listener
    We had several goroutines in which panics would crash the server process. These were being triggered by panics due to errors in doltgres. Added a recover block to each goroutine.

vitess

  • 357: Bug fix: Send an error response when the server fails to handle COM_BINLOG_DUMP_GTID
    A MySQL primary needs to be able to send back an error response when handling the COM_BINLOG_DUMP_GTID command. Previously, when the integrator returned an error, it was logged in the primary server logs, but it was not being sent back to the replica who sent the command. This change causes an error packet to be sent to the replica, containing the details of the error the integrator returned.
    This change is difficult to test in isolation, but I have tests in dolt that will exercise this codepath.
  • 356: Bug fix: Off-by-one error when parsing multiple statements
    An off-by-one error in multistatement parsing prevents us from parsing multistatements without a space between the delimiter and the next statement. For example: "SELECT 1;SELECT 2;" would previously be parsed as "SELECT 1;S" and "ELECT 2;".
    Found while testing changes for dolthub/driver#28

Closed Issues