dolt 1.42.9

[BrewTestBot]

Created by brew bump

---

Created with brew bump-formula-pr.

release notes

# Merged PRs
dolt

8219: Bug fix: events should remain enabled after sql-server restarts

Fixing an event scheduler bug that caused events to be disabled and not run when the sql-server is restarted.

Fixes Scheduled events fail to execute after a server restart dolthub/dolt#8167
8209: add constraint violations to dolt status

fixes: dolt_status table unhelpful during merge when there are constraint violations. dolthub/dolt#8114

go-mysql-server

2623: Fix anti-join correctess bug

We had some strange logic for accepting a join anti-match, ripped it out and everything seems to be working correctly now.
2620: implement name_const function

MySQL docs: https://dev.mysql.com/doc/refman/8.4/en/miscellaneous-functions.html#function_name-const
2618: More aggressively elide IN filters used for indexed lookups

re: [no-release-notes] bump for filter elide in select_random_points dolthub/dolt#8215
2617: More QueryProps, missed max1rowiter usage
2613: Query properties rule filtering

Edit most of the analyzer interfaces to pass a new context object that accumulates query specific properties. Currently the object is called QueryFlags, and accumulates information about the query to inform better rule filtering and more efficient spooling strategies.

The change that has the biggest effect on oltp_point_select perf is the sql.QFlagMax1Row setting, which lets us skip the default results iter boilerplate when we're only returning one row. Added a couple other skips for rules that are easy to whitelist correctly and show prominently on CPU profiles, like aggregations and subqueries.

vitess

361: adding instant as non-reserved keyword

The INSTANT keyword isn't in the MySQL docs, but it is a non reserved keyword.

MySQL Docs: https://dev.mysql.com/doc/refman/8.4/en/keywords.html

fixes: Correctness Issue, queries run differently on MySQL and Dolt dolthub/dolt#8220
360: Bug fix: Preserve sign for integers in prepared statements

Bound integer values for prepared statements are parsed from the wire and packaged into int64 values that are then passed to the SQL engine to execute with the prepared statement. For int8, int16, int24, and int32 types those bytes from the wire weren't getting cast to the correct type first, before they were cast to int64, which meant if the signed bit was set, the value was interpreted incorrectly.

Customer issue: CJException: 3878257648 out of range for int dolthub/dolt#8085

Closed Issues

8220: Correctness Issue, queries run differently on MySQL and Dolt
8206: Unknown JSON struct tag in schema_marshaling.go
8167: Scheduled events fail to execute after a server restart
8114: dolt_status table unhelpful during merge when there are constraint violations.

[github-actions]

🤖 An automated task has requested bottles to be published to this PR.