ob_compatibility_control

Description

ob_compatibility_control specifies the behavior when there is a compatibility conflict between MySQL 5.7 and MySQL 8.0. If you set ob_compatibility_control to MYSQL5.7, MySQL 8.0 features that do not conflict with MySQL 5.7 are not affected. You can specify the compatibility mode when you create a tenant. After a tenant is created, you cannot modify the compatibility mode.

Privilege requirements

• Query variables

  The sys tenant and all user tenants can query the value of a global system variable by using the SHOW VARIABLES statement or the information_schema.GLOBAL_VARIABLES view (MySQL-compatible mode).

• Modify variables

  After a tenant is created, you cannot modify the value of this variable by executing an SQL statement.

Attributes

Usage notes

• When you upgrade a tenant that does not have this variable to a version that has this variable, the value of this variable is MYSQL5.7 by default. When you create a new tenant, you can specify the compatibility mode.

• For features implemented in MySQL 8.0 in earlier versions, if ob_compatibility_version is earlier than 4.2.3, these features are compatible with MySQL 8.0 regardless of the value of ob_compatibility_control.

Examples

Specify the compatibility mode as MySQL 5.7 when you create a tenant.

obclient> create tenant tenant_m57 zone_list=('z1'),primary_zone='z1',resource_pool_list=('pool1') set ob_compatibility_mode='mysql',ob_compatibility_control='MYSQL5.7',ob_tcp_invited_nodes='%';

References

• ob_compatibility_version
• V$OB_COMPATIBILITY_CONTROL