MySQL protocol compatibility and precautions for application development - Lindorm

LindormTable supports access over the MySQL protocol, so you can connect with any MySQL-compatible client or driver. Before you build an application, review the defaults and constraints covered here: SSL/TLS behavior, authentication protocol selection, and the MySQL sub-protocol commands that LindormTable supports.

Prerequisites

Before you begin, make sure you have:

A Lindorm instance running LindormTable 2.6.0 or later. To check or upgrade your version, see Release notes of LindormTable and Upgrade the minor engine version of a Lindorm instance
The MySQL compatibility feature enabled. See Use a MySQL client to connect to and use LindormTable

Important

The SQL syntax supported by LindormTable is not fully compatible with MySQL syntax. For details, see Lindorm SQL syntax.

SSL/TLS

SSL encryption is enabled by default for all MySQL connections to LindormTable. LindormTable supports TLS 1.2 only.

Switch to plaintext communication

If your application and Lindorm instance are in the same Virtual Private Cloud (VPC), you can disable SSL for better performance.

For MySQL JDBC V8.x, add sslMode=disabled to the connection URL to enable plaintext communication.

Handle TLS version compatibility issues

Some older MySQL clients use TLS 1.0 or 1.1, which LindormTable does not support. If you see connection errors related to the TLS protocol version, use one of these approaches:

Switch to plaintext communication. If the application and instance are in the same VPC, disable SSL as described above.
Set the TLS version to 1.2. For MySQL JDBC V5.1.44, configure the enabledTLSProtocols parameter to specify the TLS version.
Upgrade your client. Use a client that supports MySQL 8.0 or later.

Authentication protocols

The authentication protocols available to a user depend on the LindormTable version that was running when that user was created — not the current version.

LindormTable version when user was created	Supported authentication protocols
Earlier than 2.6.2	`caching_sha2_password` only
2.6.2 or later	`caching_sha2_password` and `mysql_native_password`

Use caching_sha2_password when both protocols are available. It provides stronger security than mysql_native_password and is the default for MySQL 8.x clients.

Example: If you create a user when LindormTable is at version 2.5.4, then upgrade to 2.6.2 and create a second user, the first user supports only caching_sha2_password, while the second user supports both protocols.