Merged PRs

dolt

• 5923: Prepend table name to auto-generated constraint check names.
  Fixes #5915
• 5922: Changing schema equality to not consider tag when comparing columns
  Two tables can have identical schemas, but different column tags if the columns were created in different orders (e.g. a different sequence of alters to get to the same schema). When we try to merge those two tables, we see that there is not a common ancestor, so we require the schemas to be exactly identical in order to merge the data. This results in a confusing merge error for customers because we tell them the schemas are different, but they look exactly the same (except for the different column tags).
  This change removes column tags from equality checks when testing equality of two schemas and enables the case above to merge cleanly.
• 5913: Bh/replication metrics
  Adds some replication metrics to the prometheus metrics published by dolt.
• 5907: go/doltcore/merge: model NOT NULL constraint violations
  …olations table

go-mysql-server

• 1770: Union offset+limit bug
  Unions were dropping limit, applying offset as limit.
• 1768: CREATE LIKE statements should preserve check-constraints on the new table.
• 1767: Timezone improvements
  This PR starts handling some timezone differences between GMS and MySQL:
  • The NOW() and CURTIME() functions now respect the sessions's current time zone
  • Allows CONVERT_TZ to mix use of timezone names (e.g. UTC) and timezone offset strings (e.g. +00:00)
  • Adds some skipped tests for timestamp input/output session timezone conversion

Closed Issues

• 5915: Generated names for checks are not guarenteed to be unique.
• 5072: CREATE TABLE LIKE does not replicate CHECK constraints
• 5917: Problems uploading data with ogr2ogr (spatial data)
• 5906: Dolt is especially slow executing queries from within a loop
• 3963: Eliminate column tags, use column name for identity in all cases
• 5531: Foreign Keys can be dropped in a merge of branches that both resolve foreign keys

Latency