This release contains backwards-incompatible changes:

• information_schema tables now contain entries for revision-qualified database names (e.g. mydb/mybranch) if any are active in the current session. There is always an entry for the base database name (mydb) as well. This also applies to statements such as show databases.

In line with Dolt's version policy, this release is therefore a minor version increment (major.minor.patch)

Merged PRs

dolt

• 6210: Revert "Add dolt_schema_diff table function"
  Reverts #6185
  Change 6185 was merged in ahead of approval.
• 6204: sqle: cluster: Add dolt_cluster_transition_to_standby stored procedure.
  This new stored procedure can be used to gracefully transition a primary to a standby while not all replicas in the cluster are up and able to become current. In contrast to dolt_assume_cluster_role, this stored procedure can only transition to role standby, but takes a second integer parameter representing the number of replica servers in the cluster which must be made current in order for the transition to succeed.
• 6191: Use a table's workingRoot when getting declared FKs.
  Fixes #6178
• 6190: Ignore the sql-server.lock file if the PID in the file matches current dolt process
  #6183
  Regarding automated testing: This is an awkward one because we don't know what PID a process will be given. I tested locally with a docker images I hand crafted, but otherwise I'm going to punt on testing this in CI.
• 6188: Reverting changes to database name management: branch-qualified databases now included in info_schema tables
  Fixes #6173
• 6185: Add dolt_schema_diff table function
  dolt_schema_diff will return the schema diffs between refs and optionally will filter those changes to a specific table.
  This is a new table function that provides us with the information we need for dolt diff.
• 6162: Savepoint operations now support multiple databases in a transaction
• 6138: update dolt commit to use sql queries
  This change updates dolt commit to use the appropriate sql engine to generate results.
  Related: #3922
• 6128: Migrate dolt branch to new CLI framework.
  This PR migrates dolt branch to invoke SQL commands instead of manipulating the database directly. This allows it to work even on remote connections.
  The only thing that hasn't been migrated yet is dolt branch --datasets. It's not a documented flag. We're currently using it for an internal test and can migrate it if we can figure out a way to rewrite the test.

go-mysql-server

• 1846: update information_schema.processlist to correctly display status of processes and databases
  We used to hardcode "Query", now we reference process.Command
  Additionally, we now get the database from the current session and use that variable.
  fix for: #6023
• 1844: fix panic for group by binary type
  We made a bad type assertion for sql.StringType.
  Additionally, this fixes a issue where UnaryExpressions with GetFields would incorrectly throw a functional dependency error with ONLY_FULL_GROUP_BY enabled.
  Fix for second part of: #6179
• 1841: adding version and version_comment values
  @@version now returns 8.0.11
@@version_comment now returns "Dolt"; in mysql, this appears to be dependent on OS / method of install
  • Some people get MySQL Community Server - GPL
  • Others get Homebrew
    Fix for first part of: #6179
• 1840: deduplicate (hash) intuple for and queries
  This PR was originally supposed to fix it: original fix: dolthub/go-mysql-server#1677, but AND statements weren't covered.
  fix for: #6189
• 1838: resolve aliases in subqueries in function arguments
  The rule reorderProjection also replaces subqueries with getfields in projections when they are used by subqueries, but it did not check for function expressions.
  This meant that aliases in subqueries as arguments to functions threw a "x" could not be found error.
  This PR just has the section of reorderProjection that is supposed to find deferredColumns also look at the arguments of functions recursively (because we can nest functions).
  Additionally, there was another schema type bug:

  tmp> select 0 as foo, if((select foo), 123, 456);
  +-----+----------------------------+
  | foo | if((select foo), 123, 456) |
  +-----+----------------------------+
  | 0   | 127                        |
  +-----+----------------------------+
  1 row in set (0.00 sec)

  MySQL returns an Integer type for if statement, and if either argument is a String, it always returns a String.
  fix for: #6174
• 1836: update cached table count in prepared statements
  Prepared statements were caching table counts. We need to update the table count when finalizing prepared statements to bring table count up to date with any intermediate edits.
• 1834: fix expected schema for sum(literal)
  The code path we take when print rows to shell is different than spooling from server.
  In the sql case, we ignore the schema we get from analysis.
  In the server case, we actually read the schema, and ensure that the rows are of that type.
  When doing sum(literal), we use the type of the literal. In this issue, the literal was 1, so an INT8, which caps out at 127.
  sum() is always supposed to return a float64, so I made a change to do that.
  I checked by starting mysql with --column-type-info option, and it does appear that any columns coming from sum() has a DECIMAL type.
  Fix for: #6120
• 1827: Remove db-specific transaction interfaces / logic

vitess

• 251: Fixed missing support for collations as strings
  Fixes issue #6192
  We only allowed collations to be declared after the CREATE TABLE portion in their non-string form. This adds support for the string form.
• 249: Various small parser improvements
  Various small parser improvements:
  • Allow column definitions to use the MySQL INVISIBLE keyword. The implementation still ignores the INVISIBLE keyword, but it will no longer cause a parser error.
  • Support DOUBLE and FLOAT in the CAST and CONVERT functions.
  • Allow a trigger body to be a single CALL statement.
• 248: Support for index hint in foreign key definition
• 247: Support FK definitions inline in column definitions
  Adds support for declaring FK references inline in column definitions. Does not support ON DELETE and ON UPDATE yet. Example: ALTER TABLE t ADD COLUMN col2 int REFERENCES other_table(id);
  Also cleaned up a few rules around non-reserved keywords to enable event to be used unquoted in ALTER TABLE statements.

Closed Issues

• 6178: "SHOW CREATE TABLE foo AS OF 'bar'" shows incorrect constraints
• 6095: Allow conflict resolving for dolt_cherry_pick()
• 6192: Dolt does not allow strings as collate name
• 6179: Phpmyadmin crashes Dolt
• 6174: Unable to resolve alias in subquery in projection
• 6189: Incorrect query results for GROUP BY
• 6173: list branch-qualified databases in information_schema
• 6120: select count(1) from <table> does not return 1
• 6181: Commit/push via stored procedure is unreliable
• 6157: select count(*) from <table> confusingly slow for some users
• 1800: Extracting update query columns

Latency