Changes in MySQL Router 9.3.0 (2025-04-15, Innovation Release)

Bugs Fixed

• The check for servers from a newer series and the lack of support for servers from a newer series, introduced in MySQL Router 9.2.0, is reverted in this release.

  As of this release, MySQL Router 9.3.0 can connect to MySQL Servers from a newer series. A warning is displayed, but the connection is supported. (Bug #37690477)

  References: See also: Bug #36041256.

• Dollar-quoted strings were not supported. A syntax error was returned. (Bug #37538219)

• The http_server plugin would throw an uncaught exception and terminate when given an invalid URL. Now the exception is caught with a 400 HTTP (Bad Request) error returned to the client. (Bug #37499075)

• Improved close_connection_after_refresh=0 behavior for statements making an UPDATE statement, which would always create a new connection. Now cached connections to the PRIMARY are used for UPDATE queries, as otherwise a new connection is opened for each update. (Bug #37453301)

• It is no longer necessary to escape string values in Routing Guideline tags with \". Such string values are still supported, but not necessary. (Bug #37408429, Bug #37408370)

• If a client without the SESSION TRACK capability, or without enabling trackSessionState (MySQL Connector/J), connected to the Read/Write splitting port of MySQL Router, updates could fail with an error similar to the following:

  Press CTRL+C to copy
   
          Buffer length is less than expected payload length.

  (Bug #36374232)

• Empty and commented out statements were not allowed with Read-Write splitting enabled. (Bug #116952, Bug #37391353)

• Enabling the ANSI_QUOTES sql_mode was not allowed with Read-Write splitting enabled, and queries with it enabled would log an 'Unknown column' warning. (Bug #116950, Bug #37391347)