CREATE_SPATIAL_REFERENCE_SYSTEM privilege.  MySQL 9.2.0 introduces the CREATE_SPATIAL_REFERENCE_SYSTEM privilege, which allows the user to execute any of the following statements:

Trying to execute any of the statements just listed without having this privilege (or the SUPER privilege) now raises the error ER_CMD_NEED_SUPER_OR_CREATE_SPATIAL_REFERENCE_SYSTEM. Use of the SUPER privilege for this purpose should be considered deprecated.

See Section 8.2.2, “Privileges Provided by MySQL”, for more information.

JavaScript libraries.  The MLE component (see Section 7.5.7, “Multilingual Engine Component (MLE)”) now supports reusable JavaScript libraries containing functions which can be called from other JavaScript stored programs. Such functions must be marked as importable using the export keyword. Libraries can be managed using the CREATE LIBRARY and DROP LIBRARY SQL statements added in MySQL 9.2.0; they can be included in other stored JavaScript programs with the USING clause added in the same release to CREATE FUNCTION and CREATE PROCEDURE; USING supports a list of one or more library names.

The CREATE LIBRARY statement creates a new JavaScript library in a given database given the code for one or more JavaScript functions. JavaScript code is parsed and checked for validity at creation time; CREATE LIBRARY is rejected if the code contains any errors. DROP LIBRARY drops a given JavaScript library. Library functions can be referred to in other JavaScript stored programs using library_name.function_name notation. Libraries can be aliased as part of the USING clause with CREATE FUNCTION or CREATE PROCEDURE.

You can obtain the code contained in an existing JavaScript library using the SHOW CREATE LIBRARY statement, also implemented in MySQL 9.2.0. Additional information about JavaScript libraries can be obtained from two Information Schema tables added in MySQL 9.2.0: The LIBRARIES table provides information about JavaScript libraries; the ROUTINE_LIBRARIES provides information about stored routines using JavaScript libraries.

Counts of CREATE LIBRARY, DROP LIBRARY, and SHOW CREATE LIBRARY statements which have been issued on the server can be obtained as the status variables Com_create_library, Com_drop_library, and Com_show_create_library, respectively.

For more information, see Section 27.3.8, “Using JavaScript Libraries”.

SQL stored routine and session variable API for JavaScript.  The MLE Component in MySQL 9.2.0 and later supports access from JavaScript routines to user-defined functions, procedures, and variables.

MySQL stored functions and procedures can now be accessed using the Schema methods getFunction() and getProcedure(). Each of these functions returns a Function object which can be invoked with arguments. A stored function argument or IN parameter of a stored procedure can be passed directly; an OUT or INOUT parameter of a stored procedure requires a placeholder (an Argument object) created using mysql.arg().

In addition, MySQL user variables can now be accessed directly as properties of the JavaScript global Session object. See Accessing Session Variables from JavaScript, for more information and examples.

The 9.2.0 release also adds support for direct access to several MySQL builtin functions, listed here:

All of these functions can be called as methods of the global Mysql object.

For additional information, see Section 27.3.6.10, “Stored Routine API”, and Section 27.3.6.12, “MySQL Functions”, as well as Section 7.5.7, “Multilingual Engine Component (MLE)”.

JavaScript Transactional API.  Beginning with MySQL 9.2.0, the MLE component provides a JavaScript MySQL transaction API which performs the actions of most MySQL transactional SQL statements, such as START TRANSACTION, COMMIT, ROLLBACK, and SET AUTOCOMMIT. Support for savepoints is also included.

This work also implements an SqlError object.

For more information, see Section 27.3.6.11, “JavaScript Transaction API”, and Section 27.3.6.13, “SqlError Object”.

JavaScript ENUM and SET support.  The MySQL ENUM and SET types are supported for arguments of JavaScript stored routines in MySQL 9.2.0 and later.

For more detailed information, including rules for conversion between these MySQL types and JavaScript types, see Conversion to and from MySQL ENUM and SET.

EXPLAIN FORMAT=JSON version information.  MySQL 9.2.0 adds format version information to the output of EXPLAIN FORMAT=JSON when the JSON format version is set to 2.

To set the format version, issue SET explain_json_format_version=2 or similar. You can then see the version information in the output like this:

mysql> EXPLAIN FORMAT=JSON SELECT 1\G
*************************** 1. row ***************************
EXPLAIN: {
  "query": "/* select#1 */ select 1 AS `1`",
  "query_plan": {
    "operation": "Rows fetched before execution",
    "access_type": "rows_fetched_before_execution",
    "estimated_rows": 1.0,
    "estimated_total_cost": 0.0,
    "estimated_first_row_cost": 0.0
  },
  "query_type": "select",
  "json_schema_version": "2.0"
}
1 row in set (0.00 sec)

The output of this statement does not contain any format version information when explain_json_format_version is 1, as shown here:

mysql> SET explain_json_format_version=1;
Query OK, 0 rows affected (0.00 sec)

mysql> SELECT @@explain_json_format_version;
+-------------------------------+
| @@explain_json_format_version |
+-------------------------------+
|                             1 |
+-------------------------------+
1 row in set (0.00 sec)

mysql> EXPLAIN FORMAT=JSON SELECT 1\G
*************************** 1. row ***************************
EXPLAIN: {
  "query_block": {
    "select_id": 1,
    "message": "No tables used"
  }
}
1 row in set, 1 warning (0.00 sec)

For more information, see Obtaining Execution Plan Information, as well as the description of the explain_json_format_version system variable.

Option Tracker replication support.  The MySQL Option Tracker component, available as part of MySQL Enterprise Edition, now provides information about the binary log, the Group replication plugin, and the use of the server as a replica.

For more information, see Section 7.5.8.2, “Option Tracker Supported Components”.

Group Replication Resource Manager component.  This component, available in MySQL 9.2.0 as part of MySQL Enterprise Edition, monitors applier and recovery channel lag, as well as system resource usage, on each group secondary, and ejects any member (other than the primary) whose lag or memory usage exceeds a user-configurable limit. Expelled servers may attempt to rejoin the group if group_replication_autorejoin_tries is not equal to 0.

The Group Replication Resource Manager component checks the status of each secondary every 5 seconds, and updates a number of status variables which it provides, showing current channel lag and memory usage, as well as how many times a given threshold has been hit, and if the secondary has ever been expelled from the group, when this last occurred.

For more information, see Section 7.5.6.3, “Group Replication Resource Manager Component”.

Connection Control component.  MySQL 9.2.0 adds a Connection Control component (component_connection_control) to take the place of the Connection Control Plugins, which are now deprecated and subject to removal in a future version of MySQL.

One component replaces both of the deprecated Connection Control plugins; installation of the component requires a single INSTALL COMPONENT statement. See Section 8.4.2.1, “Connection Control Component Installation”.

The system and status variables associated with the plugin (see Section 8.4.3.2, “Connection Control Plugin System and Status Variables”) are also deprecated; see Section 8.4.2.2, “Connection Control Component Configuration” for information about the variables supported by the Connection Control component in place of the plugin variables.

The Information Schema CONNECTION_CONTROL_FAILED_LOGIN_ATTEMPTS table is also now deprecated; the component keeps counts of failed connection attempts in a Performance Schema table connection_control_failed_login_attempts.

For more information about the component_connection_control component, see Section 8.4.2, “The Connection Control Component”.

Option Tracker enhancements.  The Option Tracker component, part of MySQL Enterprise Edition, has the following improvements and enhancements in MySQL 9.2.1 and later:

See Section 7.5.8.3, “Option Tracker Status Variables”, as well as Section 7.5.8.2, “Option Tracker Supported Components”, for more information.

For more information, see Section 7.5.8.3, “Option Tracker Status Variables”. Section 7.5.8.2, “Option Tracker Supported Components”, provides information about all MySQL features supporting the Option tracker.

MySQL Enterprise Data Masking.  As of MySQL 9.2.1, MySQL Enterprise Data Masking and De-Identification is now known simply as MySQL Enterprise Data Masking.

Our documentation beginning with the 9.2 edition has been updated to reflect this change.

For more information, see Section 8.5, “MySQL Enterprise Data Masking (formerly MySQL Enterprise Data Masking and De-Identification)”.

FLUSH PRIVILEGES deprecated.  The FLUSH PRIVILEGES statement is deprecated as of MySQL 9.2.0, and causes a warning when issued. You should expect this statement to be removed in a future MySQL release.

The following constructs are also deprecated in MySQL 9.2.0:

In addition, the following features do not cause any warnings but should be considered deprecated:

For more information, see Section 15.7.8.3, “FLUSH Statement”.

Version Tokens plugin.  The Version Tokens plugin is deprecated as of MySQL 9.2.0, and subject to removal in a future MySQL release. Attempting to install the version_tokens plugin, or to start the server when the plugin is installed, causes a deprecation warning to be issued. The following related features are also deprecated in MySQL 9.2.0, and raise deprecation warnings whenever they are invoked:

BINLOG keyword now restricted.  The BINLOG keyword is now restricted, and can no longer be used unquoted as a label in a MySQL stored routine or stored function. You should update any affected applications accordingly, before upgrading to MySQL 9.2.

See Section 11.3, “Keywords and Reserved Words”, for more information.