The following types of Session object are available:
NodeSession: Use this session type for new application development to communicate with MySQL server instances which have the X Protocol enabled. It offers the best integration with MySQL Server, and therefore, it is used by default.
ClassicSession Use this session type to interact with MySQL Servers that do not have the X Protocol enabled. The development API available for this type of session is very limited. For example, there are no CRUD operations, no collection handling, and binding is not supported.
ClassicSession is specific to MySQL Shell
and cannot be used with other implementations of
X DevAPI, such as MySQL Connectors.
MySQL Shell creates a Session object by default. You can
either configure the session type using MySQL Shell command
scheme element of a URI type
string, or provide an option to the
\connect command. To choose which type of
session should be created when starting MySQL Shell, use one
of these options:
To choose which type of session to use when defining a URI type string use one of these options:
mysqlxto create an X Protocol session. The X Plugin must be installed on the server instance, see Chapter 19, Using MySQL as a Document Store for more information.
mysqlto create a classic MySQL protocol session.
For more information, see Section 126.96.36.199, “Connecting using a URI String”.
If you open MySQL Shell without specifying connection
parameters, MySQL Shell opens without an established global
session. It is possible to establish a global session once
MySQL Shell has been started using the MySQL Shell
URI is a URI type
string as defined at
Section 188.8.131.52, “Connecting using a URI String”. For
\connect URI: Creates a Node session. Attempts to use X Protocol by default, and falls back to MySQL protocol.
\connect -n URI: Creates a Node session.
\connect -c URI: Creates a ClassicSession using MySQL protocol.
mysql-js> \connect mysqlx://user@localhost:33060
Alternatively, use the
method. For example this is equivalent to the above