Merged PRs

dolt

• 6164: Bug fix: Enable dolt_cherry_pick stored procedure to work with @@autocommit
  Previously, when dolt_cherry_pick encountered a data or schema conflict, or a constraint violation, it would return an error with a message about the problem and how to resolve. This works well when @@autocommit=0, but when @@autocommit=1 the error causes the automatic transaction management to automatically rollback the changes, which prevents users from being able to examine and fix the conflicts.
  This PR changes dolt_cherry_pick to be more similar to how dolt_merge reports conflicts – instead of returning an error message, dolt_cherry_pick now returns additional fields that show the number of tables with data conflicts, number of tables with schema conflicts, and number of tables with constraint violations.

go-mysql-server

• 1823: Trim spaces and empty statements to the right in planbuilder.Parse
• 1807: add support for more JSON_TABLE() functionality
  This PR adds support for:
  • FOR ORDINALITY columns, which is just an auto increment
  • DEFAULT <value> ON ERROR/EMPTY , which fills in values when encountering either an error or a missing value
  • when this isn't specified, NULL is used
  • ERROR <value> on ERROR/EMPTY, which throws an error when encountering either an error or a missing value
  • when this isn't specified, we ignore errors and fill in values with NULL
  • NESTED columns, which is a way to extract data from objects within objects and so on
  • when there are multiple NESTED columns, they are "sibling" nested, they take turns being NULL
    Note: there is a skipped test highlighting a bug in either our jsonpath implementation or it's something here...
    Companion PR: dolthub/vitess#240
    MySQL docs: https://dev.mysql.com/doc/refman/8.0/en/json-table-functions.html

vitess

• 245: allow event as table and column name
  The PR allows EVENT non-reserved keyword to be used as table and column name without quoting.
  The missing edge case includes using EVENT for user name or host name.
• 240: Support more JSON_TABLE functionality
  Source: https://dev.mysql.com/doc/refman/8.0/en/json-table-functions.html

  JSON_TABLE(
  expr,
  path COLUMNS (column_list)
  )   [AS] alias
  column_list:
  column[, column][, ...]
  column:
  name FOR ORDINALITY
  |  name type PATH string path [on_empty] [on_error]
  |  name type EXISTS PATH string path
  |  NESTED [PATH] path COLUMNS (column_list)
  on_empty:
  {NULL | DEFAULT json_string | ERROR} ON EMPTY
  on_error:
  {NULL | DEFAULT json_string | ERROR} ON ERROR
  

  Note: the MySQL docs indicate that PATH is optional in the NESTED case, but it doesn't seem that way.
  I chose to follow what they say rather than what they do.

Closed Issues

Latency