Merged PRs

dolt

• 9841: Validate that FKs referencing system tables don't specify referential actions
• 9832: Reverted Extended encoding from adaptive to ref
  While working on importing dumps in Doltgres, I found out that data wasn't being written correctly in some circumstances. Turns out that the new adaptive encoding is incomplete, and therefore broken, and any columns over the inline threshold will be truncated. This truncation results in a panic whenever the field is read, since the serialized size does not match the data, causing OOB access.
  This should be safe to change since existing databases will simply swap to using the old ref approach until adaptive is fixed, where we can then swap back to the adaptive encoding (since the ref code is still in the codebase). I've already spoken to Nick who will lead the fix once he has returned next week.

go-mysql-server

• 3219: dolthub/go-mysql-server#3216: Fix UNION ALL with NULL BLOB SELECT returning NULL for all vals
  Fixes #3216
• 3215: Trim strings before converting to bool
  fixes #9821
  fixes #9834
• 3214: Implement PIPES_AS_CONCAT mode
  Fixes #9791
  depends on dolthub/vitess#432
• 3204: #9812: Coalesce IN and = operator logic
  Fixes #9812

vitess

• 432: Implement PIPES_AS_CONCAT mode parsing
  Part of #9791
• 426: Length-encode vector values when sent on the wire.
  GMS uses Vitess code to encode responses into the MySQL wire format.
  Testing for this change is in the corresponding GMS PR.

Closed Issues

• 9791: PIPES_AS_CONCAT sql_mode not yet implemented in Dolt - || operator behavior differs from MySQL
• 9834: Missing warning on invalid numeric conversion
• 9821: Logical operators with numeric string incorrectly evaluates to FALSE
• 3216: No binary data from UNION ALL