Backwards Incompatible Changes

There has been a type change on the dolt_diff system table with provides more precision and alignment with the dolt_diff_{table} system table. There is a remote possibility that this could impact existing applications, and client code may require updates to remain consistent.

Per Dolt’s versioning policy, this is a minor version bump because these changes may impact existing applications. Please reach out to us on GitHub or Discord if you have questions or need help with any of these changes.

Merged PRs

dolt

• 9129: More precision on the date column in the dolt_diff table
  Use higher precision date type in the dolt_diff table - matching dolt_diff_{table} now
  Fixes: #9126

go-mysql-server

• 2943: refactor and implement TimestampAdd()
  This PR implements the TimestampAdd; it is treated as basically an alias for DateAdd().
  mysql docs: https://dev.mysql.com/doc/refman/8.4/en/date-and-time-functions.html#function_timestampadd
  fix: #9117
• 2940: Bug fix: ensure DropCheck.IfExists gets copied over to new instances
  This change doesn't affect Dolt, but is needed by Doltgres to make sure IF EXISTS logic for dropping a constraint is correctly executed.

vitess

• 412: allow trim, cast, and position as nonkeywords
  This PR adds makes it so that TRIM, CAST and POSITION are usable as table and column names without backquotes.
  fixes: #9123
• 410: fix ntile syntax
  This PR implements the correct syntax for NTILE()
  mysql docs: https://dev.mysql.com/doc/refman/8.4/en/window-function-descriptions.html#function_ntile
  syntax for: #9087

Closed Issues

• 9126: dolt_diff vs dolt_diff_ - commit time precision differs
• 9123: BUG: Dolt treats position as a reserved keyword
• 9117: BUG: Panic in GMS when using TIMESTAMPADD()
• 6901: sql TIME type is not supported in Dolt

Performance