Details
-
New Feature
-
Status: Open (View Workflow)
-
Major
-
Resolution: Unresolved
-
None
-
None
Description
The CREATE SERVER statement only currently supports the following options:
- HOST - The hostname or IP address to use when connecting to the remote server. This option is mututally exclusive with SOCKET.
- PORT - The port to use when connecting to the remote server. This option is mututally exclusive with SOCKET.
- SOCKET - The path to the Unix socket file to use when connecting to the remote server. This option is mututally exclusive with HOST and PORT.
- USER - The username to use when connecting to the remote server.
- PASSWORD - The password to use when connecting to the remote server.
- DATABASE - The database to select when connecting to the remote server.
- OWNER - This option is not currently used for anything, so you can use it to store a comment.
Since these are connectivity-related options, I think it would make sense to add the following TLS-related options as well:
- SSLCA
- SSLCAPATH
- SSLCERT
- SSLKEY
- SSLCIPHER
- TLSVERSION
(For Spider, I do understand that TLS-related options can be set in the table's COMMENT field. However, it would make sense if you could define them in the CREATE SERVER statement, if you wanted to do so.)
If we add a bunch of new options, then would it also make sense to change the mysql.servers table to use JSON as well to make the format more flexible?
Attachments
Issue Links
- is blocked by
-
MDEV-34716 Allow arbitrary options in CREATE SERVER
- Closed
- relates to
-
MDEV-22541 CREATE SERVER does not treat SOCKET as mutually exclusive from HOST and PORT
- Open
-
MDEV-27106 Spider: specify connection to data node by engine-defined attributes
- Closed
-
MDEV-34272 Implement ODBC Connection Keywords (aka parameters) as OPTIONS for CREATE SERVER
- Closed