Table of Contents
This chapter introduces an alternative way of working with MySQL as a document store, sometimes referred to as “using NoSQL”. If your intention is to use MySQL in a traditional (SQL) way, this chapter is probably not relevant to you.
Using MySQL as a document store is currently a preproduction feature to which this notice applies: Section 3.1, “Preproduction Status — Legal Notice”.
Relational databases such as MySQL usually required a document schema to be defined before documents can be stored. The features described in this section enable you to use MySQL as a document store, which is a schema-less, and therefore schema-flexible, storage system for documents. When using MySQL as a document store, to create documents describing products you do not need to know and define all possible attributes of any products before storing them and operating with them. This differs from working with a relational database and storing products in a table, when all columns of the table must be known and defined before adding any products to the database. The features described in this chapter enable you to choose how you configure MySQL, using only the document store model, or combining the flexibility of the document store model with the power of the relational model.
These sections cover the usage of MySQL as a document store:
The Section 3.2, “Key Concepts” section covers concepts like Document, Collection, Session, and Schema to help you understand how to use MySQL as a document store.
The Section 3.3, “Setting Up MySQL as a Document Store” section explains how to configure X Plugin on a MySQL Server, so it can function as a document store, and how to install MySQL Shell to use as a client.
The MySQL Shell is an interactive interface to MySQL supporting JavaScript, Python, or SQL modes. You can use the MySQL Shell to prototype applications, execute queries and update data. The quick-start guides (tutorials) help you to get started using MySQL Shell.
The quick-start guide for JavaScript is here: Section 3.4, “Quick-Start Guide: MySQL Shell for JavaScript”.
The quick-start guide for Python is here: Section 3.5, “Quick-Start Guide: MySQL Shell for Python”.
Section 3.8, “MySQL Shell User Guide” provides more detailed information about using MySQL Shell.
X DevAPI User guide.
Clients that communicate with a MySQL Server using the X Protocol can use the X DevAPI to develop applications. For example MySQL Shell and MySQL Connectors provide this ability by implementing the X DevAPI. X DevAPI offers a modern programming interface with a simple yet powerful design which provides support for established industry standard concepts. See X DevAPI User Guide for in-depth tutorials on using X DevAPI.
The following MySQL Connectors support the X Protocol and enable you to use X DevAPI in your chosen language to develop applications that communicate with a MySQL Server functioning as a document store.
Each implementation of X DevAPI provides library reference documentation, available at the above links.
This documentation is in preproduction status and is intended for demonstration and preliminary use only. It may not be specific to the hardware on which you are using the software. Oracle Corporation and its affiliates are not responsible for and expressly disclaim all warranties of any kind with respect to this documentation and will not be responsible for any loss, costs, or damages incurred due to the use of this documentation.
This section explains the concepts introduced as part of using MySQL as a document store.
A Document is a set of key and value pairs, as represented by a JSON object. A Document is represented internally using the MySQL binary JSON object, through the JSON MySQL datatype. The values of fields can contain other documents, arrays, and lists of documents.
{ "GNP": .6, "IndepYear": 1967, "Name": "Sealand", "_id": "SEA", "demographics": { "LifeExpectancy": 79, "Population": 27 }, "geography": { "Continent": "Europe", "Region": "British Islands", "SurfaceArea": 193 }, "government": { "GovernmentForm": "Monarchy", "HeadOfState": "Michael Bates" } }
Create, Read, Update and Delete (CRUD) operations are the four basic operations that can be performed on a database Collection or Table. In terms of MySQL this means:
Create a new entry (insertion or addition)
Read entries (queries)
Update entries
Delete entries
The MySQL Server plugin which enables communication using X Protocol. Supports clients that implement X DevAPI and enables you to use MySQL as a document store.
This section describes how to install the X Plugin to enable MySQL Server to use the X Protocol and use MySQL Shell to act as a client to the server.
The prerequisite for using MySQL as a document store is the X Plugin, which implements the X Protocol. Without the X Plugin running, X Protocol clients cannot connect to the server. The X Plugin is shipped with MySQL (5.7.12 or higher) — installing it does not involve a separate download.
Setting up MySQL as a document store follows the steps outlined here:
Install or upgrade to MySQL 5.7.12 or higher.
When the installation or upgrade is done, start the server. For server startup instructions, see Section 2.10.2, “Starting the Server”.
MySQL Installer enables you to perform this and the next step (Install the X Plugin) at the same time for new installations on Microsoft Windows. In the Plugin and Extensions screen, check mark the Enable X Protocol/MySQL as a Document Store check box. After the installation, verify that the X Plugin has been installed.
Install the X Plugin. A
non-root account can be used to install the plugin as long as
the account has INSERT
privilege
for the mysql.plugin
table.
Always save your existing configuration settings before reconfiguring the server.
To install the built-in X Plugin, do one of the following:
Using MySQL Installer for Windows:
Launch MySQL Installer for Windows. MySQL Installer dashboard opens.
Click the Reconfigure quick action for MySQL Server. Use and to configure the following items:
In Accounts and Roles, confirm
the current root
account
password.
In Plugin and Extensions, check mark the Enable X Protocol/MySQL as a Document Store check box. MySQL Installer provides a default port number and opens the firewall port for network access.
In Apply Server Configuration, click Execute.
Click
to close MySQL Installer.Using MySQL Shell:
Open a terminal window (command prompt on Windows) and
navigate to the MySQL binaries location (for example,
/usr/bin/
on Linux).
Run the following command:
mysqlsh -u user
-h localhost --classic --dba enableXProtocol
Using the MySQL Client program:
Open a terminal window (command prompt on Windows) and
navigate to the MySQL binaries location (for example,
/usr/bin/
on Linux).
Invoke the mysql command-line client:
mysql -u user
-p
Issue the following statement:
mysql> INSTALL PLUGIN mysqlx SONAME 'mysqlx.so';
Replace mysqlx.so
with
mysqlx.dll
for Windows.
Verify that the X Plugin has been installed.
When the X Plugin is installed properly, it shows up in the list when you query for active plugins on the server with one of the following commands:
MySQL Shell command:
mysqlsh -u user
--sqlc -e "show plugins"
MySQL Client program command:
mysql -u user
-p -e "show plugins"
If you encounter problems with the X Plugin installation, or if you want to learn about alternative ways of installing, configuring, or uninstalling server plugins, see Section 6.5.2, “Installing and Uninstalling Plugins”.
mysqlxsys@localhost
User Account
Installing the X Plugin creates a
mysqlxsys@localhost
user account. If, for some
reason, creating the user account fails, the X Plugin
installation fails, too. Here is an explanation on what the
mysqlxsys@localhost
user account is for and what
to do when its creation fails.
The X Plugin installation process uses the MySQL
root
user to create an internal account for the
mysqlxsys@localhost
user. The
mysqlxsys@localhost
account is used by the
X Plugin for authentication of external users against the
MySQL account system and for killing sessions when requested by a
privileged user. The mysqlxsys@localhost
account
is created as locked, so it cannot be used to log in by external
users. If for some reason the MySQL root
account
is not available, before you start the X Plugin installation
you must manually create the mysqlxsys@localhost
user by issuing the following statements in the
mysql command-line client:
CREATE USER IF NOT EXISTS mysqlxsys@localhost IDENTIFIED WITH
mysql_native_password AS 'password' ACCOUNT LOCK;
GRANT SELECT ON mysql.user TO mysqlxsys@localhost;
GRANT SUPER ON *.* TO mysqlxsys@localhost;
If you ever want to uninstall (deactivate) the X Plugin, issue the following statement in the mysql command-line client:
UNINSTALL PLUGIN mysqlx;
Do not use MySQL Shell to issue the previous statement. It works from MySQL Shell, but you get an error (code 1130). Also, uninstalling the plugin removes the mysqlxsys user.
This section describes how to download, install, and start MySQL Shell, which is an interactive JavaScript, Python, or SQL interface supporting development and administration for the MySQL Server. MySQL Shell is a component of MySQL 5.7.12 or higher that you can install separately.
MySQL Shell is available on Microsoft Windows, Linux, and OS X for 64-bit platforms. MySQL Shell requires that the built-in X Plugin be active for MySQL 5.7.12 or higher. You can install the server plugin before or after you install MySQL Shell. For instructions, see Installing the X Plugin.
To install MySQL Shell on Microsoft Windows using the MSI Installer, do the following:
Download the Windows (x86, 64-bit), MSI Installer package from http://dev.mysql.com/downloads/shell/.
When prompted, click
.Follow the steps in the Setup Wizard.
If you have installed MySQL without enabling the X Plugin, then later on decide you want to install the X Plugin, or if you are installing MySQL without using MySQL Installer, see Installing the X Plugin.
Installation packages for MySQL Shell are available only for a limited number of Linux distributions, and only for 64-bit systems.
For supported Linux distributions, the easiest way to install MySQL Shell on Linux is to use the MySQL APT repository or MySQL Yum repository. For systems not using the MySQL repositories, MySQL Shell can also be downloaded and installed directly.
Installation of MySQL Shell using the MySQL APT repository is only supported on Ubuntu 14.04 LTS (“Trusty Tahr”) and Ubuntu 15.10 (“Wily Werewolf”).
For Linux distributions supported by the MySQL APT repository, follow one of the paths below:
If you do not yet have the MySQL APT repository as a software repository on your system, do the following:
Follow the steps given in Adding the MySQL APT Repository, paying special attention to the following:
During the installation of the configuration package, when asked in the dialogue box to configure the repository, make sure you choose MySQL 5.7 (which is the default option) as the release series you want, and enable the
component.Make sure you do not skip the step for updating package information for the MySQL APT repository:
sudo apt-get update
Install MySQL Shell with this command:
sudo apt-get install mysql-shell
If you already have the MySQL APT repository as a software repository on your system, do the following:
Update package information for the MySQL APT repository:
sudo apt-get update
Update the MySQL APT repository configuration package with the following command:
sudo apt-get install mysql-apt-config
When asked in the dialogue box to configure the repository, make sure you choose MySQL 5.7 (which is the default option) as the release series you want, and enable the
component.Install MySQL Shell with this command:
sudo apt-get install mysql-shell
Installation of MySQL Shell using the MySQL Yum repository is only supported on EL6 and EL7-based systems, as well as Fedora 23 and 24.
For Linux distributions supported by the MySQL Yum repository, follow these steps to install MySQL Shell:
Do one of the following:
If you already have the
MySQL Yum
repository as a software repository on your
system and the repository was configured with the new
release package
mysql57-community-release
, skip to
the next step (“Enable the MySQL Tools Preview
subrepository...”).
If you already have the
MySQL Yum
repository as a software repository on your
system but have configured the repository with the old
release package
mysql-community-release
, it is
easiest to install MySQL Shell by first
reconfiguring the MySQL Yum repository with the new
mysql57-community-release
package.
To do so, you need to remove your old release package
first, with the following command :
sudo yum remove mysql-community-release
For dnf-enabled systems, do this instead:
sudo dnf erase mysql-community-release
Then, follow the steps given in
Adding
the MySQL Yum Repository to install the new
release package,
mysql57-community-release
.
If you do not yet have the MySQL Yum repository as a software repository on your system, follow the steps given in Adding the MySQL Yum Repository.
Enable the MySQL Tools Preview subrepository. You can do
that by editing manually the
/etc/yum.repos.d/mysql-community.repo
file. This is an example of the subrepository's default
entry in the file (the baseurl
entry in
your file might look different, depending on your Linux
distribution):
[mysql-tools-preview] name=MySQL Tools Preview baseurl=http://repo.mysql.com/yum/mysql-tools-preview/el/6/$basearch/ enabled=0 gpgcheck=1 gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-mysql
Change the entry enabled=0
to
enabled=1
to enable the subrepository.
Install MySQL Shell with this command:
sudo yum install mysql-shell
For dnf-enabled systems, do this instead:
sudo dnf install mysql-shell
RPM, Debian, and source packages for installing MySQL Shell are also available for download at Download MySQL Shell.
To install MySQL Shell on OS X, do the following:
Download the package from http://dev.mysql.com/downloads/shell/.
Double-click the downloaded DMG to mount it. Finder opens.
Double-click the .pkg
file shown in the
Finder window.
Follow the steps in the installation wizard.
When the installer finishes, eject the DMG. (It can be deleted.)
You need an account name and password to establish a session using
MySQL Shell. Replace user
with your
account name.
On the same system where the server instance is running, open a terminal window (command prompt on Windows) and start MySQL Shell with the following command:
mysqlsh --uri user
@localhost
You are prompted to input your password and then this establishes an X Session.
For instructions to get you started using MySQL Shell and MySQL as a document store, see the following quick-start guides:
This quick-start guide provides instructions to begin prototyping database applications interactively with MySQL Shell. The guide includes the following topics:
Introduction to MySQL functionality, MySQL Shell, and the
world_x
database sample.
Operations to manage collections and documents.
Operations to manage relational tables.
Operations that apply to documents within tables.
Section 3.8, “MySQL Shell User Guide” provides more in-depth information about MySQL Shell.
X DevAPI User Guide provides more examples of using X DevAPI.
The MySQL Shell for JavaScript quick start provides a short but comprehensive introduction to the database functionality introduced with MySQL 5.7.12. This functionality includes the new X DevAPI, which offers a modern, integrative way to work with relational and document data, without requiring SQL knowledge from application developers.
In MySQL, tables are the native data storage container type and collections are stored internally using tables.
A JSON document is a data structure composed of field/value pairs stored within a collection. The values of fields often contain other documents, arrays, and lists of documents.
{ "GNP": .6, "IndepYear": 1967, "Name": "Sealand", "_id": "SEA", "demographics": { "LifeExpectancy": 79, "Population": 27 }, "geography": { "Continent": "Europe", "Region": "British Islands", "SurfaceArea": 193 }, "government": { "GovernmentForm": "Monarchy", "HeadOfState": "Michael Bates" } }
A table in MySQL enables you to store data organized in rows and columns. The structure of a table is defined by one or more columns with user-defined names and data types. Every row stored in the table has the same structure.
+------+------------------+-------------+-----------------+------------------------+ | ID | Name | CountryCode | District | Info | +------+------------------+-------------+-----------------+------------------------+ | 1 | Kabul | AFG | Kabol |{"Population": 1780000} | | 2 | Qandahar | AFG | Qandahar |{"Population": 237500} | | 3 | Herat | AFG | Herat |{"Population": 186800} | | 4 | Mazar-e-Sharif | AFG | Balkh |{"Population": 127800} | | 5 | Amsterdam | NLD | Noord-Holland |{"Population": 731200} | | 6 | Rotterdam | NLD | Zuid-Holland |{"Population": 593321} | +------+------------------+-------------+-----------------+------------------------+
Section 3.8, “MySQL Shell User Guide” provides a general overview.
See X DevAPI User Guide for development reference documentation.
The world_x
database sample contains one JSON
collection and a set of three relational tables:
Collection
CountryInfo: Information about countries in the world.
Tables
Country: Minimal information about countries of the world.
City: Information about some of the cities in those countries.
CountryLanguage: Languages spoken in each country.
You must install MySQL Shell and MySQL 5.7.12 or higher with the X Protocol enabled. For instructions, see Section 3.3, “Setting Up MySQL as a Document Store”.
Start the server before you load the world_x
database for this guide.
To prepare the world_x
database sample,
follow these steps:
Download world_x-db.zip.
Extract the installation archive to a temporary location
such as /tmp/
. Unpacking the archive
results in a single file named
world_x.sql
.
Create or recreate the schema with the following command:
mysqlsh -u root --sql --recreate-schema world_x < /tmp/world_x-db/world_x.sql
Enter password:****
Recreating schema world_x...
Enter your password when prompted. A non-root account can be used as long as the account has privileges to create new databases.
Replace /tmp/
with the path to the
world_x.sql
file on your system.
Section 3.8.2.1, “MySQL Shell Sessions” explains session types.
See Chapter 2, Installing and Upgrading MySQL for general installation assistance.
MySQL Shell is a unified scripting interface to MySQL Server. It supports scripting in JavaScript and Python. JavaScript is the default processing mode. In most cases, you need an account to connect to the local MySQL server instance.
After you have installed and started MySQL server, connect MySQL Shell to the server instance. By default, MySQL Shell connects using the X Protocol.
On the same system where the server instance is running, open a terminal window and start MySQL Shell with the following command:
mysqlsh -u
Creating an X Session toname
world_xname
@localhost:33060/world_x Enter password:****
You may need to specify the path as appropriate.
In addition:
name
represents the user name of
your MySQL account.
MySQL Shell prompts you for your password.
The default schema for this session is the
world_x
database. For instructions on
setting up the world_x
database sample,
see
Section 3.4.2, “Import Database Sample”.
The mysql-js>
prompt indicates that the
active language for this session is JavaScript.
mysql-js>
When you run mysqlsh without the host argument, MySQL Shell attempts to connect to the server instance running on the localhost interface on port 33060. To specify a different host or port number, as well as other options, see the option descriptions at Section 5.5.7, “mysqlsh — The MySQL Shell”.
MySQL Shell supports input-line editing as follows:
left-arrow and right-arrow keys move horizontally within the current input line.
up-arrow and down-arrow keys move up and down through the set of previously entered lines.
Backspace deletes the character before the cursor and typing new characters enters them at the cursor position.
Enter enters the current input line.
Type mysqlsh --help at the prompt of your command interpreter for a list of command-line options.
mysqlsh --help
Type \help at the MySQL Shell prompt for a list of available commands and their descriptions.
mysql-js> \help
Type \help followed by a command name for detailed help about an individual MySQL Shell command. For example, to view help on the \connect command, type:
mysql-js> \help \connect
See Section 3.8.3.1, “Interactive Code Execution” for an explanation of how interactive code execution works in MySQL Shell.
See Section 3.8.2, “Getting Started with MySQL Shell” to learn about session and connection alternatives.
In MySQL, collections contain JSON documents that you can add, find, update, and remove. Collections are containers within a schema that you create, list, and drop.
The examples in this section use the CountryInfo collection in the
world_x
database. For instructions on setting
up the world_x
database sample, see
Section 3.4.2, “Import Database Sample”.
In MySQL, documents are represented as JSON objects. Internally, they are stored in an efficient binary format that enables fast lookups and updates.
Simple document format:
{field1: "value", field2 : 10, "field 3": null}
An array of documents consists of a set of documents separated by
commas and enclosed within [
and
]
characters.
Simple array of documents:
[{Name: "Aruba", _id: "ABW"}, {Name: "Angola", _id: "AGO"}]
MySQL supports the following value types in JSON documents:
numbers (integer and floating point)
strings
boolean (false and true)
null
arrays of more JSON values
nested (or embedded) objects of more JSON values
Collections are containers for documents that share a purpose and possibly share one or more indexes. Each collection has a unique name and exists within a single schema.
The term schema is equivalent to a database, which means a group of database objects (as opposed to relational schema used to enforce structure and constraints over data). A schema does not enforce conformity on the documents in a collection.
In this quick-start guide:
Basic objects include:
Object form | Description |
---|---|
db | db is a global variable assigned to the current
active schema that you specified on the command line.
You can type db in MySQL Shell to
print a description of the object, which in this case
will be the name of the schema it represents. |
db.getCollections() | db.getCollections() holds a list of collections in the schema. Use the list to get references to collection objects, iterate over them, and so on. |
Basic operations scoped by collections include:
Operation form | Description |
---|---|
db. | The add() method inserts one document or a list of documents into the named collection. |
db. | The find() method returns some or all documents in the named collection. |
db. | The modify() method updates documents in the named collection. |
db. | The remove() method deletes one document or a list of documents from the named collection. |
See Working with Collections for a general overview.
CRUD EBNF Definitions provides a complete list of operations.
In MySQL Shell, you can create new collections, get a list of the existing collections in a schema, and remove an existing collection from a schema. Collection names are case-sensitive and each collection name must be unique.
To show the value that is assigned to the schema variable,
type db
.
mysql-js> db
<Schema:world_x>
If the schema value is not Schema:world_x
,
then set the db
variable as follows:
mysql-js> \use world_x
Schema `world_x` accessible through db.
To create a new collection in an existing schema, use the
createCollection()
method.
The following example creates in the
world_x
database a collection called flags.
The method returns a collection object.
mysql-js> db.createCollection("flags")
<Collection:flags>
To display all collections in the world_x
database, use the getCollections()
method
on the schema object. Collections returned by the server
appear between curly braces.
mysql-js> db.getCollections()
{
"CountryInfo": <Collection:CountryInfo>,
"flags": <Collection:flags>
}
To drop an existing collection from a database, use the
dropCollection()
method on the session
object. For example, to drop the flags collection from the
world_x
database, type:
mysql-js> session.dropCollection("world_x", "flags")
Query OK (0.04 sec)
See Section 3.8.2.2.6, “Connections in JavaScript and Python” to learn more about the session object.
See Collection Objects for more examples.
You can use the add()
method to insert one
document or a list documents into an existing collection using
MySQL Shell. All examples in this section use the CountryInfo
collection.
To show the value that is assigned to the schema variable,
type db
.
mysql-js> db
<Schema:world_x>
If the schema value is not Schema:world_x
,
then set the db
variable as follows:
mysql-js> \use world_x
Schema `world_x` accessible through db.
Insert the following document into the CountryInfo collection. Press Enter twice to insert the document.
mysql-js> db.CountryInfo.add(
{
GNP: .6,
IndepYear: 1967,
Name: "Sealand",
_id: "SEA",
demographics: {
LifeExpectancy: 79,
Population: 27
},
geography: {
Continent: "Europe",
Region: "British Islands",
SurfaceArea: 193
},
government: {
GovernmentForm: "Monarchy",
HeadOfState: "Michael Bates"
}
}
)
Query OK, 1 item affected (0.02 sec)
The method returns the status of the operation.
Each document requires an identifier field called
_id
. The value of the
_id
field must be unique among all
documents in the same collection. If the document passed to
the add()
method does not contain the
_id
field, MySQL Shell automatically
inserts a field into the document and sets the value to a
generated universal unique identifier (UUID).
See CollectionAddFunction for the full syntax definition.
You can use the find()
method to query for
and return documents from a collection in a database.
MySQL Shell provides additional methods to use with the
find()
method to filter and sort the returned
documents.
MySQL provides the following operators to specify search
conditions: OR
(||
),
AND
(&&
),
XOR
, IS
,
NOT
, BETWEEN
,
IN
, LIKE
,
!=
, <>
,
>
, >=
,
<
, <=
,
&
, |
,
<<
, >>
,
+
, -
,
*
, /
,
~
, and %
.
To return all documents in a collection, use the
find()
method without specifying search
conditions. For example, the following operation returns all
documents in the CountryInfo collection.
mysql-js> db.CountryInfo.find()
[
{
"GNP": 828,
"IndepYear": null,
"Name": "Aruba",
"_id": "ABW",
"demographics": {
"LifeExpectancy": 78.4000015258789,
"Population": 103000
},
"geography": {
"Continent": "North America",
"Region": "Caribbean",
"SurfaceArea": 193
},
"government": {
"GovernmentForm": "Nonmetropolitan Territory of The Netherlands",
"HeadOfState": "Beatrix"
}
...
}
]
240 documents in set (0.00 sec)
The method produces results that contain operational information in addition to all documents in the collection.
An empty set (no matching documents) returns the following information:
Empty set (0.00 sec)
You can include search conditions with the
find()
method. The syntax for expressions
that form a search condition is the same as that of
traditional MySQL. You must
enclose all expressions in quotes.
All examples in this section use the CountryInfo collection in
the world_x
database. For the sake of
brevity, some of the examples do not display output.
A simple search condition consists of the
_id
field and unique identifier of a
document. The following example returns a single document
matching the identifier string:
mysql-js> db.CountryInfo.find("_id = 'AUS'")
[
{
"GNP": 351182,
"IndepYear": 1901,
"Name": "Australia",
"_id": "AUS",
"demographics": {
"LifeExpectancy": 79.80000305175781,
"Population": 18886000
},
"geography": {
"Continent": "Oceania",
"Region": "Australia and New Zealand",
"SurfaceArea": 7741220
},
"government": {
"GovernmentForm": "Constitutional Monarchy, Federation",
"HeadOfState": "Elisabeth II"
}
}
]
1 document in set (0.01 sec)
The following example searches for all countries that have a GNP higher than $500 billion. The CountryInfo collection measures GNP in units of million.
mysql-js> db.CountryInfo.find("GNP > 500000")
...[output removed]
10 documents in set (0.00 sec)
The Population field in the following query is embedded within the demographics object. To access the embedded field, use a period between demographics and Population to identify the relationship. Document and field names are case sensitive.
mysql-js> db.CountryInfo.find("GNP > 500000 and demographics.Population < 100000000")
...[output removed]
6 documents in set (0.00 sec)
Arithmetic operators in the following expression are used to query for countries with a GNP per capita higher than $30000. Search conditions can include arithmetic operators and most MySQL functions.
Seven documents in the CountryInfo collection have a population value of zero. Warning messages appear at the end of the output.
mysql-js> db.CountryInfo.find("GNP*1000000/demographics.Population > 30000")
...[output removed]
9 documents in set, 7 warnings (0.00 sec)
Warning (Code 1365): Division by 0
Warning (Code 1365): Division by 0
Warning (Code 1365): Division by 0
Warning (Code 1365): Division by 0
Warning (Code 1365): Division by 0
Warning (Code 1365): Division by 0
Warning (Code 1365): Division by 0
You can separate a value from the search condition by using
the bind()
method. For example, instead of
specifying a hard-coded country name as the condition,
substitute a named placeholder consisting of a colon followed
by a name that begins with a letter, such as
country. Then include the placeholder and
value in the bind()
method as follows:
mysql-js> db.CountryInfo.find("Name = :country").bind("country", "Italy")
[
{
"GNP": 1161755,
"IndepYear": 1861,
"Name": "Italy",
"_id": "ITA",
"demographics": {
"LifeExpectancy": 79,
"Population": 57680000
},
"geography": {
"Continent": "Europe",
"Region": "Southern Europe",
"SurfaceArea": 301316
},
"government": {
"GovernmentForm": "Republic",
"HeadOfState": "Carlo Azeglio Ciampi"
}
}
]
1 document in set (0.01 sec)
Within a program, binding enables you to specify placeholders in your expressions, which are filled in with values before execution and can benefit from automatic escaping, as appropriate.
Always use binding to sanitize input. Avoid introducing values in queries using string concatenation, which can produce invalid input and, in some cases, can cause security issues.
You can return specific fields of a document, instead of returning all the fields. The following example returns the GNP and Name fields of all documents in the CountryInfo collection matching the search conditions.
Use the fields()
method to pass the list of
fields to return.
mysql-js> db.CountryInfo.find("GNP > 5000000").fields(["GNP", "Name"])
[
{
"GNP": 8510700,
"Name": "United States"
}
]
1 document in set (0.00 sec)
In addition, you can alter the returned documents—adding, renaming, nesting and even computing new field values—with an expression that describes the document to return.
First, use the following statement to import the mysqlx module:
mysql-js> var mysqlx = require('mysqlx').mysqlx;
Next, alter the names of the fields with the following expression to return only two documents.
mysql-js> db.CountryInfo.find().
fields(mysqlx.expr('{"Name": upper(Name), "GNPPerCapita": GNP*1000000/demographics.Population}')).
limit(2)
[
{
"GNPPerCapita": 8038.834951456311,
"Name": "ARUBA"
},
{
"GNPPerCapita": 263.0281690140845,
"Name": "AFGHANISTAN"
}
]
2 documents in set (0.00 sec)
You can apply the limit()
,
sort()
, and skip()
methods to manage the number and order of documents returned
by the find()
method.
To specify the number of documents included in a result set,
append the limit()
method with a value to
the find()
method. The following query
returns the first five documents in the CountryInfo
collection.
mysql-js> db.CountryInfo.find().limit(5)
... [output removed]
5 documents in set (0.00 sec)
To specify an order for the results, append the
sort()
method to the
find()
method. Pass to the
sort()
method a list of one or more fields
to sort by and, optionally, the descending
(desc
) or ascending
(asc
) attribute as appropriate. Ascending
order is the default order type.
For example, the following query sorts all documents by the IndepYear field and then returns the first eight documents in descending order.
mysql-js> db.CountryInfo.find().sort(["IndepYear desc"]).limit(8)
... [output removed]
8 documents in set (0.00 sec)
By default, the limit()
method starts from
the first document in the collection. You can use the
skip()
method to change the starting
document. For example, to ignore the first document and return
the next eight documents matching the condition, pass to the
skip()
method a value of 1.
mysql-js> db.CountryInfo.find().sort(["IndepYear desc"]).limit(8).skip(1)
... [output removed]
8 documents in set (0.00 sec)
The MySQL Reference Manual provides detailed documentation on functions and operators.
See CollectionFindFunction for the full syntax definition.
You can use the modify()
method to update one
or more documents in a collection. The X DevAPI provides
additional methods for use with the modify()
method to:
Set and unset fields within documents.
Append, insert, and delete arrays.
Bind, limit, and sort the documents to be modified.
The modify()
method works by filtering a
collection to include only the documents to be modified and
then applying the operations that you specify to those
documents.
In the following example, the modify()
method uses the search condition to identify the document to
change and then the set()
method replaces
two values within the nested demographics object.
mysql-js> db.CountryInfo.modify("_id = 'SEA'").
set("demographics", {LifeExpectancy: 78, Population: 28})
Query OK, 1 item affected (0.04 sec)
After you modify a document, use the find()
method to verify the change.
To remove content from a document, use the
modify()
and unset()
methods. For example, the following query removes the GNP from
a document that matches the search condition.
mysql-js> db.CountryInfo.modify("Name = 'Sealand'").unset("GNP")
Query OK, 1 item affected (0.01 sec)
Use the find()
method to verify the change.
mysql-js> db.CountryInfo.find("Name = 'Sealand'")
[
{
"IndepYear": 1967,
"Name": "Sealand",
"_id": "SEA",
"demographics": {
"LifeExpectancy": 78,
"Population": 28
},
"geography": {
"Continent": "Europe",
"Region": "British Islands",
"SurfaceArea": 193
},
"government": {
"GovernmentForm": "Monarchy",
"HeadOfState": "Michael Bates"
}
}
]
1 document in set (0.00 sec)
To append an element to an array field, or insert, or delete
elements in an array, use the
arrayAppend()
,
arrayInsert()
, or
arrayDelete()
methods. The following
examples modify the CountryInfo collection to enable tracking
of international airports.
The first example uses the modify()
and
set()
methods to create a new Airports
field in all documents.
Use care when you modify documents without specifying a search condition. This action will modify all documents in the collection.
mysql-js> db.CountryInfo.modify().set("Airports", [])
Query OK, 240 items affected (0.07 sec)
With the Airports field added, the next example uses the
arrayAppend()
method to add a new airport
to one of the documents. $.Airports in
the following example represents the Airports field of the
current document.
mysql-js> db.CountryInfo.modify("Name = 'France'").arrayAppend("$.Airports", "ORY")
Query OK, 1 item affected (0.02 sec)
Use db.CountryInfo.find("Name =
'France'")
to see the change.
To insert an element at a different position in the array, use
the arrayInsert()
method to specify which
index to insert in the path expression. In this case, the
index is 0, or the first element in the array.
mysql-js> db.CountryInfo.modify("Name = 'France'").arrayInsert("$.Airports[0]", "CDG")
Query OK, 1 item affected (0.04 sec)
To delete an element from the array, you must pass to the
arrayDelete()
method the index of the
element to be deleted.
mysql-js> db.CountryInfo.modify("Name = 'France'").arrayDelete("$.Airports[1]")
Query OK, 1 item affected (0.03 sec)
The MySQL Reference Manual provides instructions to help you search for and modify JSON values.
See CollectionModifyFunction for the full syntax definition.
You can use the remove()
method to delete
some or all documents from a collection in a database. The
X DevAPI provides additional methods for use with the
remove()
method to filter and sort the
documents to be removed.
The example that follows passes a search condition to the
remove()
method. All documents matching the
condition will be removed from the CountryInfo collection. In
this example, one document matches the condition.
mysql-js> db.CountryInfo.remove("_id = 'SEA'")
Query OK, 1 item affected (0.02 sec)
To remove the first document in the CountryInfo collection,
use the limit()
method with a value of 1.
mysql-js> db.CountryInfo.remove().limit(1)
Query OK, 1 item affected (0.03 sec)
The following example removes the last document in the CountryInfo collection by country name.
mysql-js> db.CountryInfo.remove().sort(["Name desc"]).limit(1)
Query OK, 1 item affected (0.02 sec)
You can remove all documents in a collection. To do so, use
the remove()
method without specifying a
search condition.
Use care when you remove documents without specifying a search condition. This action will delete all documents in the collection.
See CollectionRemoveFunction for the full syntax definition.
See
Section 3.4.2, “Import Database Sample”
for instructions to recreate the
world_x
database.
Indexes are used to find documents with specific field values quickly. Without an index, MySQL must begin with the first document and then read through the entire collection to find the relevant fields. The larger the collection, the more this costs. If a collection is large and queries on a specific field are common, then consider creating an index on a specific field inside a document.
For example, the following query will perform better with an index:
mysql-js> db.CountryInfo.find("demographics.Population < 100")
...[output removed]
8 documents in set (0.00 sec)
The createIndex()
method creates an index
that you can define as nonunique or unique. Use the
field()
method to chain the fields that
should be indexed. The execute()
method is
required to create or drop an index.
In MySQL, the _id
field is equivalent to a
primary key by default.
To create a nonunique index, pass to the
createIndex()
method an index name.
Duplicate index names are prohibited.
In the following example, the first parameter of the
field()
method specifies the Population
field inside the demographics object and the next parameter
indicates that the field should be indexed as an Integer
numeric value. The last parameter indicates whether the field
should require the NOT NULL constraint. If the value is
false
, the field can contain
NULL
values.
mysql-js> db.CountryInfo.createIndex("pop").
field("demographics.Population", "INTEGER", false).execute()
Query OK (0.04 sec)
To create a unique index, pass to the
createIndex()
method an index name and the
mysqlx.IndexType.Unique
type. The following
statement imports the mysqlx module, which is required to
specify an index type:
mysql-js> var mysqlx = require('mysqlx').mysqlx;
Country "Name"
is another common field in
the CountryInfo collection to index. In the following example,
"Text(40)"
represents the number of
characters to index and true
indicates that
the field cannot contain any NULL
values.
mysql-js> db.CountryInfo.createIndex("name", mysqlx.IndexType.Unique).
field("Name", "TEXT(40)", true).execute()
Query OK (0.04 sec)
To drop an index, pass to the dropIndex()
method the name of the index to drop. For example, you can
drop the “pop” index as follows:
mysql-js> db.CountryInfo.dropIndex("pop").execute()
Query OK (0.58 sec)
See Collection Index Management Functions for the full syntax definition.
You can use MySQL Shell to manipulate not just JSON documents, but also relational tables.
In MySQL, each relational table is associated with a particular
storage engine. The examples in this section use
InnoDB
tables in the
world_x
database.
To show the value that is assigned to the schema variable, type
db
.
mysql-js> db
<Schema:world_x>
If the schema value is not Schema:world_x
, then
set the db
variable as follows:
mysql-js> \use world_x
Schema `world_x` accessible through db.
To display all relational tables in the world_x
database, use the getTables()
method on the
schema object.
mysql-js> db.getTables()
{
"City": <Table:City>,
"Country": <Table:Country>,
"CountryLanguage": <Table:CountryLanguage>
}
Basic operations scoped by tables include:
Operation form | Description |
---|---|
db. | The insert() method inserts one or more records into the named table. |
db. | The select() method returns some or all records in the named table. |
db. | The update() method updates records in the named table. |
db. | The delete() method deletes one or more records from the named table. |
See Working with Relational Tables for a general overview.
CRUD EBNF Definitions provides a complete list of operations.
See Section 3.4.2, “Import Database Sample”
for instructions on setting up the world_x
database sample.
You can use the insert()
method with the
values()
method to insert records into an
existing relational table. The insert()
method accepts individual columns or all columns in the table.
Use one or more values()
methods to specify
the values to be inserted.
To insert a complete record, pass to the
insert()
method all columns in the table.
Then pass to the values()
method one value
for each column in the table. For example, to add a new record
to the City table in the world_x
database,
insert the following record and press Enter
twice.
mysql-js> db.City.insert("ID", "Name", "CountryCode", "District", "Info").
values(null, "Olympia", "USA", "Washington", '{"Population": 5000}')
Query OK, 1 item affected (0.01 sec)
The City table has five columns: ID, Name, CountryCode, District, and Info. Each value must match the data type of the column it represents.
The following example inserts values into the ID, Name, and CountryCode columns of the City table.
mysql-js> db.City.insert("ID", "Name", "CountryCode").
values(null, "Little Falls", "USA").values(null, "Happy Valley", "USA")
Query OK, 2 item affected (0.03 sec)
When you specify columns using the insert()
method, the number of values must match the number of columns.
In the previous example, you must supply three values to match
the three columns specified.
See TableInsertFunction for the full syntax definition.
You can use the select()
method to query for
and return records from a table in a database. The
X DevAPI provides additional methods to use with the
select()
method to filter and sort the
returned records.
MySQL provides the following operators to specify search
conditions: OR
(||
),
AND
(&&
),
XOR
, IS
,
NOT
, BETWEEN
,
IN
, LIKE
,
!=
, <>
,
>
, >=
,
<
, <=
,
&
, |
,
<<
, >>
,
+
, -
,
*
, /
,
~
, and %
.
To issue a query that returns all records from an existing
table, use the select()
method without
specifying search conditions. The following example selects
all records from the City table in the
world_x
database.
Limit the use of the empty select()
method to interactive statements. Always use explicit
column-name selections in your application code.
mysql-js> db.City.select()
+------+------------+-------------+------------+-------------------------+
| ID | Name | CountryCode | District | Info |
+------+------------+-------------+------------+-------------------------+
| 1 | Kabul | AFG | Kabol |{"Population": 1780000} |
| 2 | Qandahar | AFG | Qandahar |{"Population": 237500} |
| 3 | Herat | AFG | Herat |{"Population": 186800} |
... ... ... ... ...
| 4079 | Rafah | PSE | Rafah |{"Population": 92020} |
+------+------- ----+-------------+------------+-------------------------+
4082 rows in set (0.01 sec)
An empty set (no matching records) returns the following information:
Empty set (0.00 sec)
To issue a query that returns a set of table columns, use the
select()
method and specify the columns to
return between square brackets. This query returns the Name
and CountryCode columns from the City table.
mysql-js> db.City.select(["Name", "CountryCode"])
+-------------------+-------------+
| Name | CountryCode |
+-------------------+-------------+
| Kabul | AFG |
| Qandahar | AFG |
| Herat | AFG |
| Mazar-e-Sharif | AFG |
| Amsterdam | NLD |
... ...
| Rafah | PSE |
| Olympia | USA |
| Little Falls | USA |
| Happy Valley | USA |
+-------------------+-------------+
4082 rows in set (0.00 sec)
To issue a query that returns rows matching specific search
conditions, use the where()
method to
include those conditions. For example, the following example
returns the names and country codes of the cities that start
with the letter Z.
mysql-js> db.City.select(["Name", "CountryCode"]).where("Name like 'Z%'")
+-------------------+-------------+
| Name | CountryCode |
+-------------------+-------------+
| Zaanstad | NLD |
| Zoetermeer | NLD |
| Zwolle | NLD |
| Zenica | BIH |
| Zagazig | EGY |
| Zaragoza | ESP |
| Zamboanga | PHL |
| Zahedan | IRN |
| Zanjan | IRN |
| Zabol | IRN |
| Zama | JPN |
| Zhezqazghan | KAZ |
| Zhengzhou | CHN |
... ...
| Zeleznogorsk | RUS |
+-------------------+-------------+
59 rows in set (0.00 sec)
You can separate a value from the search condition by using
the bind()
method. For example, instead of
using "Name = 'Z%' " as the condition, substitute a named
placeholder consisting of a colon followed by a name that
begins with a letter, such as name. Then
include the placeholder and value in the
bind()
method as follows:
mysql-js> db.City.select(["Name", "CountryCode"]).
where("Name like :name").bind("name", "Z%")
Within a program, binding enables you to specify placeholders in your expressions, which are filled in with values before execution and can benefit from automatic escaping, as appropriate.
Always use binding to sanitize input. Avoid introducing values in queries using string concatenation, which can produce invalid input and, in some cases, can cause security issues.
To issue a query using the AND
operator, add the operator between search conditions in the
where()
method.
mysql-js> db.City.select(["Name", "CountryCode"]).
where("Name like 'Z%' and CountryCode = 'CHN'")
+----------------+-------------+
| Name | CountryCode |
+----------------+-------------+
| Zhengzhou | CHN |
| Zibo | CHN |
| Zhangjiakou | CHN |
| Zhuzhou | CHN |
| Zhangjiang | CHN |
| Zigong | CHN |
| Zaozhuang | CHN |
... ...
| Zhangjiagang | CHN |
+----------------+-------------+
22 rows in set (0.01 sec)
To specify multiple conditional operators, you can enclose the
search conditions in parenthesis to change the operator
precedence. The following example demonstrates the placement
of AND
and
OR
operators.
mysql-js> db.City.select(["Name", "CountryCode"]).
where("Name like 'Z%' and (CountryCode = 'CHN' or CountryCode = 'RUS')")
+-------------------+-------------+
| Name | CountryCode |
+-------------------+-------------+
| Zhengzhou | CHN |
| Zibo | CHN |
| Zhangjiakou | CHN |
| Zhuzhou | CHN |
... ...
| Zeleznogorsk | RUS |
+-------------------+-------------+
29 rows in set (0.01 sec)
You can apply the limit()
,
orderBy()
, and offSet()
methods to manage the number and order of records returned by
the select()
method.
To specify the number of records included in a result set,
append the limit()
method with a value to
the select()
method. For example, the
following query returns the first five records in the Country
table.
mysql-js> db.Country.select(["Code", "Name"]).limit(5)
+------+-------------+
| Code | Name |
+------+-------------+
| ABW | Aruba |
| AFG | Afghanistan |
| AGO | Angola |
| AIA | Anguilla |
| ALB | Albania |
+------+-------------+
5 rows in set (0.00 sec)
To specify an order for the results, append the
orderBy()
method to the
select()
method. Pass to the
orderBy()
method a list of one or more
columns to sort by and, optionally, the descending
(desc
) or ascending
(asc
) attribute as appropriate. Ascending
order is the default order type.
For example, the following query sorts all records by the Name column and then returns the first three records in descending order .
mysql-js> db.Country.select(["Code", "Name"]).orderBy(["Name desc"]).limit(3)
+------+------------+
| Code | Name |
+------+------------+
| ZWE | Zimbabwe |
| ZMB | Zambia |
| YUG | Yugoslavia |
+------+------------+
3 rows in set (0.00 sec)
By default, the limit()
method starts from
the first record in the table. You can use the
offset()
method to change the starting
record. For example, to ignore the first record and return the
next three records matching the condition, pass to the
offset()
method a value of 1.
mysql-js> db.Country.select(["Code", "Name"]).orderBy(["Name desc"]).limit(3).offset(1)
+------+------------+
| Code | Name |
+------+------------+
| ZMB | Zambia |
| YUG | Yugoslavia |
| YEM | Yemen |
+------+------------+
3 rows in set (0.00 sec)
The MySQL Reference Manual provides detailed documentation on functions and operators.
See TableSelectFunction for the full syntax definition.
You can use the update()
method to modify one
or more records in a table. The update()
method works by filtering a query to include only the records to
be updated and then applying the operations you specify to those
records.
To replace a city name in the City table, pass to the
set()
method the new city name. Then, pass to
the where()
method the city name to locate
and replace. The following example replaces the city Peking with
Beijing.
mysql-js> db.City.update().set("Name", "Beijing").where("Name = 'Peking'")
Query OK, 1 item affected (0.04 sec)
Use the select()
method to verify the change.
mysql-js> db.City.select(["ID", "Name", "CountryCode", "District", "Info"]).where("Name = 'Beijing'")
+------+-----------+-------------+----------+-----------------------------+
| ID | Name | CountryCode | District | Info |
+------+-----------+-------------+----------+-----------------------------+
| 1891 | Beijing | CHN | Peking | {"Population": 7472000} |
+------+-----------+-------------+----------+-----------------------------+
1 row in set (0.00 sec)
See TableUpdateFunction for the full syntax definition.
You can use the delete()
method to remove
some or all records from a table in a database. The
X DevAPI provides additional methods to use with the
delete()
method to filter and order the
records to be deleted.
The example that follows passes search conditions to the
delete()
method. All records matching the
condition will be deleted from the City table. In this
example, one record matches the condition.
mysql-js> db.City.delete().where("Name = 'Olympia'")
Query OK, 1 item affected (0.01 sec)
To delete the first record in the City table, use the
limit()
method with a value of 1.
mysql-js> db.City.delete().limit(1)
Query OK, 1 item affected (0.02 sec)
You can delete all records in a table. To do so, use the
delete()
method without specifying a search
condition.
Use care when you delete records without specifying a search condition. This action will delete all records from the table.
See TableDeleteFunction for the full syntax definition.
See
Section 3.4.2, “Import Database Sample”
for instructions to recreate the
world_x
database.
In MySQL, a table may contain traditional relational data, JSON
values, or both. You can combine traditional data with JSON
documents by storing the documents in columns having a native
JSON
data type.
Examples in this section use the City table in the
world_x
database.
The City table has five columns (or fields).
+---------------+------------+-------+-------+---------+------------------+ | Field | Type | Null | Key | Default | Extra | +---------------+------------+-------+-------+---------+------------------+ | ID | int(11) | NO | PRI | null | auto_increment | | Name | char(35) | NO | | | | | CountryCode | char(3) | NO | | | | | District | char(20) | NO | | | | | Info | json | YES | | null | | +---------------+------------+-------+-------+---------+------------------+
To insert a document into the column of a table, pass to the
values()
method a well-formed JSON document
in the correct order. In the following example, a document is
passed as the final value to be inserted into the Info column.
mysql-js> db.City.insert().
values(null, "San Francisco", "USA", "California", '{"Population":830000}')
Query OK, 1 item affected (0.01 sec)
You can issue a query with a search condition that evaluates document values in the expression.
mysql-js> db.City.select(["ID", "Name", "CountryCode", "District", "Info"]).
where("CountryCode = :country and Info->'$.Population' > 1000000").
bind('country', 'USA')
+------+----------------+-------------+----------------+-----------------------------+
| ID | Name | CountryCode | District | Info |
+------+----------------+-------------+----------------+-----------------------------+
| 3793 | New York | USA | New York | {"Population": 8008278} |
| 3794 | Los Angeles | USA | California | {"Population": 3694820} |
| 3795 | Chicago | USA | Illinois | {"Population": 2896016} |
| 3796 | Houston | USA | Texas | {"Population": 1953631} |
| 3797 | Philadelphia | USA | Pennsylvania | {"Population": 1517550} |
| 3798 | Phoenix | USA | Arizona | {"Population": 1321045} |
| 3799 | San Diego | USA | California | {"Population": 1223400} |
| 3800 | Dallas | USA | Texas | {"Population": 1188580} |
| 3801 | San Antonio | USA | Texas | {"Population": 1144646} |
+------+----------------+-------------+----------------+-----------------------------+
9 rows in set (0.01 sec)
See Working with Relational Tables and Documents for a general overview.
See Section 12.6, “The JSON Data Type” for a detailed description of the data type.
This quick-start guide provides instructions to begin prototyping database applications interactively with MySQL Shell. The guide includes the following topics:
Introduction to MySQL functionality, MySQL Shell, and the
world_x
database sample.
Operations to manage collections and documents.
Operations to manage relational tables.
Operations that apply to documents within tables.
Section 3.8, “MySQL Shell User Guide” provides more in-depth information about MySQL Shell.
X DevAPI User Guide provides more examples of using X DevAPI.
The MySQL Shell for Python quick start provides a short but comprehensive introduction to the database functionality introduced with MySQL 5.7.12. This functionality includes the new X DevAPI, which offers a modern, integrative way to work with relational and document data, without requiring SQL knowledge from application developers.
In MySQL, tables are the native data storage container type and collections are stored internally using tables.
A JSON document is a data structure composed of field/value pairs stored within a collection. The values of fields often contain other documents, arrays, and lists of documents.
{ "GNP": .6, "IndepYear": 1967, "Name": "Sealand", "_id": "SEA", "demographics": { "LifeExpectancy": 79, "Population": 27 }, "geography": { "Continent": "Europe", "Region": "British Islands", "SurfaceArea": 193 }, "government": { "GovernmentForm": "Monarchy", "HeadOfState": "Michael Bates" } }
A table in MySQL enables you to store data organized in rows and columns. The structure of a table is defined by one or more columns with user-defined names and data types. Every row stored in the table has the same structure.
+------+------------------+-------------+-----------------+------------------------+ | ID | Name | CountryCode | District | Info | +------+------------------+-------------+-----------------+------------------------+ | 1 | Kabul | AFG | Kabol |{"Population": 1780000} | | 2 | Qandahar | AFG | Qandahar |{"Population": 237500} | | 3 | Herat | AFG | Herat |{"Population": 186800} | | 4 | Mazar-e-Sharif | AFG | Balkh |{"Population": 127800} | | 5 | Amsterdam | NLD | Noord-Holland |{"Population": 731200} | | 6 | Rotterdam | NLD | Zuid-Holland |{"Population": 593321} | +------+------------------+-------------+-----------------+------------------------+
Section 3.8, “MySQL Shell User Guide” provides a general overview.
See X DevAPI User Guide for development reference documentation.
The world_x
database sample contains one JSON
collection and a set of three relational tables:
Collection
CountryInfo: Information about countries in the world.
Tables
Country: Minimal information about countries of the world.
City: Information about some of the cities in those countries.
CountryLanguage: Languages spoken in each country.
You must install MySQL Shell and MySQL 5.7.12 or higher with the X Protocol enabled. For instructions, see Section 3.3, “Setting Up MySQL as a Document Store”.
Start the server before you load the world_x
database for this guide.
To prepare the world_x
database sample,
follow these steps:
Download world_x-db.zip.
Extract the installation archive to a temporary location
such as /tmp/
. Unpacking the archive
results in a single file named
world_x.sql
.
Create or recreate the schema with the following command:
mysqlsh -u root --sql --recreate-schema world_x < /tmp/world_x-db/world_x.sql
Enter password:****
Recreating schema world_x...
Enter your password when prompted. A non-root account can be used as long as the account has privileges to create new databases.
Replace /tmp/
with the path to the
world_x.sql
file on your system.
Section 3.8.2.1, “MySQL Shell Sessions” explains session types.
See Chapter 2, Installing and Upgrading MySQL for general installation assistance.
MySQL Shell is a unified scripting interface to MySQL Server. It supports scripting in JavaScript and Python. JavaScript is the default processing mode. In most cases, you need an account to connect to the local MySQL server instance.
After you have installed and started MySQL server, connect MySQL Shell to the server instance. By default, MySQL Shell connects using the X Protocol.
On the same system where the server instance is running, open a terminal window and start MySQL Shell with the following command:
mysqlsh -u
Creating an X Session toname
--py world_xname
@localhost:33060/world_x Enter password:****
You may need to specify the path as appropriate.
In addition:
name
represents the user name of
your MySQL account.
MySQL Shell prompts you for your password.
The --py
option starts MySQL Shell in
Python mode. If you omit --py
,
MySQL Shell starts in JavaScript mode.
The default schema for this session is the
world_x
database. For instructions on
setting up the world_x
database sample,
see Section 3.5.2, “Import Database Sample”.
The mysql-py>
prompt indicates that the
active language for this session is Python.
mysql-py>
When you run mysqlsh without the host argument, MySQL Shell attempts to connect to the server instance running on the localhost interface on port 33060. To specify a different host or port number, as well as other options, see the option descriptions at Section 5.5.7, “mysqlsh — The MySQL Shell”.
MySQL Shell supports input-line editing as follows:
left-arrow and right-arrow keys move horizontally within the current input line.
up-arrow and down-arrow keys move up and down through the set of previously entered lines.
Backspace deletes the character before the cursor and typing new characters enters them at the cursor position.
Enter enters the current input line.
Type mysqlsh --help at the prompt of your command interpreter for a list of command-line options.
mysqlsh --help
Type \help at the MySQL Shell prompt for a list of available commands and their descriptions.
mysql-py> \help
Type \help followed by a command name for detailed help about an individual MySQL Shell command. For example, to view help on the \connect command, type:
mysql-py> \help \connect
See Section 3.8.3.1, “Interactive Code Execution” for an explanation of how interactive code execution works in MySQL Shell.
See Section 3.8.2, “Getting Started with MySQL Shell” to learn about session and connection alternatives.
In MySQL, collections contain JSON documents that you can add, find, update, and remove. Collections are containers within a schema that you create, list, and drop.
The examples in this section use the CountryInfo collection in the
world_x
database. For instructions on setting
up the world_x
database sample, see
Section 3.5.2, “Import Database Sample”.
In MySQL, documents are represented as JSON objects. Internally, they are stored in an efficient binary format that enables fast lookups and updates.
Simple document format:
{"field1": "value", "field2" : 10, "field 3": null}
An array of documents consists of a set of documents separated by
commas and enclosed within [
and
]
characters.
Simple array of documents:
[{"Name": "Aruba", "_id": "ABW"}, {"Name": "Angola", "_id": "AGO"}]
MySQL supports the following value types in JSON documents:
numbers (integer and floating point)
strings
boolean (False and True)
None
arrays of more JSON values
nested (or embedded) objects of more JSON values
Collections are containers for documents that share a purpose and possibly share one or more indexes. Each collection has a unique name and exists within a single schema.
The term schema is equivalent to a database, which means a group of database objects (as opposed to relational schema used to enforce structure and constraints over data). A schema does not enforce conformity on the documents in a collection.
In this quick-start guide:
Basic objects include:
Object form | Description |
---|---|
db | db is a global variable assigned to the current
active schema that you specified on the command line.
You can type db in MySQL Shell to
print a description of the object, which in this case
will be the name of the schema it represents. |
db.getCollections() | db.getCollections() holds a list of collections in the schema. Use the list to get references to collection objects, iterate over them, and so on. |
Basic operations scoped by collections include:
Operation form | Description |
---|---|
db. | The add() method inserts one document or a list of documents into the named collection. |
db. | The find() method returns some or all documents in the named collection. |
db. | The modify() method updates documents in the named collection. |
db. | The remove() method deletes one document or a list of documents from the named collection. |
See Working with Collections for a general overview.
CRUD EBNF Definitions provides a complete list of operations.
In MySQL Shell, you can create new collections, get a list of the existing collections in a schema, and remove an existing collection from a schema. Collection names are case-sensitive and each collection name must be unique.
To show the value that is assigned to the schema variable,
type db
.
mysql-py> db
<Schema:world_x>
If the schema value is not Schema:world_x
,
then set the db
variable as follows:
mysql-py> \use world_x
Schema `world_x` accessible through db.
To create a new collection in an existing schema, use the
createCollection()
method.
The following example creates in the
world_x
database a collection called flags.
The method returns a collection object.
mysql-py> db.createCollection("flags")
<Collection:flags>
To display all collections in the world_x
database, use the getCollections()
method
on the schema object. Collections returned by the server
appear between curly braces.
mysql-py> db.getCollections()
{
"CountryInfo": <Collection:CountryInfo>,
"flags": <Collection:flags>
}
To drop an existing collection from a database, use the
dropCollection()
method on the session
object. For example, to drop the flags collection from the
world_x
database, type:
mysql-py> session.dropCollection("world_x", "flags")
Query OK (0.04 sec)
See Section 3.8.2.2.6, “Connections in JavaScript and Python” to learn more about the session object.
See Collection Objects for more examples.
You can use the add()
method to insert one
document or a list documents into an existing collection using
MySQL Shell. All examples in this section use the CountryInfo
collection.
To show the value that is assigned to the schema variable,
typedb
.
mysql-py> db
<Schema:world_x>
If the schema value is not Schema:world_x
,
then set the db
variable as follows:
mysql-py> \use world_x
Schema `world_x` accessible through db.
Insert the following document into the CountryInfo collection. Press Enter twice to insert the document.
mysql-py> db.CountryInfo.add(
{
"GNP": .6,
"IndepYear": 1967,
"Name": "Sealand",
"_id": "SEA",
"demographics": {
"LifeExpectancy": 79,
"Population": 27
},
"geography": {
"Continent": "Europe",
"Region": "British Islands",
"SurfaceArea": 193
},
"government": {
"GovernmentForm": "Monarchy",
"HeadOfState": "Michael Bates"
}
}
)
Query OK, 1 item affected (0.02 sec)
The method returns the status of the operation.
Each document requires an identifier field called
_id
. The value of the
_id
field must be unique among all
documents in the same collection. If the document passed to
the add()
method does not contain the
_id
field, MySQL Shell automatically
inserts a field into the document and sets the value to a
generated universal unique identifier (UUID).
See CollectionAddFunction for the full syntax definition.
You can use the find()
method to query for
and return documents from a collection in a database.
MySQL Shell provides additional methods to use with the
find()
method to filter and sort the returned
documents.
MySQL provides the following operators to specify search
conditions: OR
(||
),
AND
(&&
),
XOR
, IS
,
NOT
, BETWEEN
,
IN
, LIKE
,
!=
, <>
,
>
, >=
,
<
, <=
,
&
, |
,
<<
, >>
,
+
, -
,
*
, /
,
~
, and %
.
To return all documents in a collection, use the
find()
method without specifying search
conditions. For example, the following operation returns all
documents in the CountryInfo collection.
mysql-py> db.CountryInfo.find()
[
{
"GNP": 828,
"IndepYear": null,
"Name": "Aruba",
"_id": "ABW",
"demographics": {
"LifeExpectancy": 78.4000015258789,
"Population": 103000
},
"geography": {
"Continent": "North America",
"Region": "Caribbean",
"SurfaceArea": 193
},
"government": {
"GovernmentForm": "Nonmetropolitan Territory of The Netherlands",
"HeadOfState": "Beatrix"
}
...
}
]
240 documents in set (0.00 sec)
The method produces results that contain operational information in addition to all documents in the collection.
An empty set (no matching documents) returns the following information:
Empty set (0.00 sec)
You can include search conditions with the
find()
method. The syntax for expressions
that form a search condition is the same as that of
traditional MySQL. You must
enclose all expressions in quotes.
All examples in this section use the CountryInfo collection in
the world_x
database. For the sake of
brevity, some of the examples do not display output.
A simple search condition consists of the
_id
field and unique identifier of a
document. The following example returns a single document
matching the identifier string:
mysql-py> db.CountryInfo.find("_id = 'AUS'")
[
{
"GNP": 351182,
"IndepYear": 1901,
"Name": "Australia",
"_id": "AUS",
"demographics": {
"LifeExpectancy": 79.80000305175781,
"Population": 18886000
},
"geography": {
"Continent": "Oceania",
"Region": "Australia and New Zealand",
"SurfaceArea": 7741220
},
"government": {
"GovernmentForm": "Constitutional Monarchy, Federation",
"HeadOfState": "Elisabeth II"
}
}
]
1 document in set (0.01 sec)
The following example searches for all countries that have a GNP higher than $500 billion. The CountryInfo collection measures GNP in units of million.
mysql-py> db.CountryInfo.find("GNP > 500000")
...[output removed]
10 documents in set (0.00 sec)
The Population field in the following query is embedded within the demographics object. To access the embedded field, use a period between demographics and Population to identify the relationship. Document and field names are case sensitive.
mysql-py> db.CountryInfo.find("GNP > 500000 and demographics.Population < 100000000")
...[output removed]
6 documents in set (0.00 sec)
Arithmetic operators in the following expression are used to query for countries with a GNP per capita higher than $30000. Search conditions can include arithmetic operators and most MySQL functions.
Seven documents in the CountryInfo collection have a population value of zero. Warning messages appear at the end of the output.
mysql-py> db.CountryInfo.find("GNP*1000000/demographics.Population > 30000")
...[output removed]
9 documents in set, 7 warnings (0.00 sec)
Warning (Code 1365): Division by 0
Warning (Code 1365): Division by 0
Warning (Code 1365): Division by 0
Warning (Code 1365): Division by 0
Warning (Code 1365): Division by 0
Warning (Code 1365): Division by 0
Warning (Code 1365): Division by 0
You can separate a value from the search condition by using
the bind()
method. For example, instead of
specifying a hard-coded country name as the condition,
substitute a named placeholder consisting of a colon followed
by a name that begins with a letter, such as
country. Then include the placeholder and
value in the bind()
method as follows:
mysql-py> db.CountryInfo.find("Name = :country").bind("country", "Italy")
[
{
"GNP": 1161755,
"IndepYear": 1861,
"Name": "Italy",
"_id": "ITA",
"demographics": {
"LifeExpectancy": 79,
"Population": 57680000
},
"geography": {
"Continent": "Europe",
"Region": "Southern Europe",
"SurfaceArea": 301316
},
"government": {
"GovernmentForm": "Republic",
"HeadOfState": "Carlo Azeglio Ciampi"
}
}
]
1 document in set (0.01 sec)
Within a program, binding enables you to specify placeholders in your expressions, which are filled in with values before execution and can benefit from automatic escaping, as appropriate.
Always use binding to sanitize input. Avoid introducing values in queries using string concatenation, which can produce invalid input and, in some cases, can cause security issues.
You can return specific fields of a document, instead of returning all the fields. The following example returns the GNP and Name fields of all documents in the CountryInfo collection matching the search conditions.
Use the fields()
method to pass the list of
fields to return.
mysql-py> db.CountryInfo.find("GNP > 5000000").fields(["GNP", "Name"])
[
{
"GNP": 8510700,
"Name": "United States"
}
]
1 document in set (0.00 sec)
In addition, you can alter the returned documents—adding, renaming, nesting and even computing new field values—with an expression that describes the document to return.
First, use the following statement to import the mysqlx module:
mysql-py> import mysqlx
Next, alter the names of the fields with the following expression to return only two documents.
mysql-py> db.CountryInfo.find().\
fields(mysqlx.expr('{"Name": upper(Name), "GNPPerCapita": GNP*1000000/demographics.Population}')).\
limit(2)
[
{
"GNPPerCapita": 8038.834951456311,
"Name": "ARUBA"
},
{
"GNPPerCapita": 263.0281690140845,
"Name": "AFGHANISTAN"
}
]
2 documents in set (0.00 sec)
You can apply the limit()
,
sort()
, and skip()
methods to manage the number and order of documents returned
by the find()
method.
To specify the number of documents included in a result set,
append the limit()
method with a value to
the find()
method. The following query
returns the first five documents in the CountryInfo
collection.
mysql-py> db.CountryInfo.find().limit(5)
... [output removed]
5 documents in set (0.00 sec)
To specify an order for the results, append the
sort()
method to the
find()
method. Pass to the
sort()
method a list of one or more fields
to sort by and, optionally, the descending
(desc
) or ascending
(asc
) attribute as appropriate. Ascending
order is the default order type.
For example, the following query sorts all documents by the IndepYear field and then returns the first eight documents in descending order.
mysql-py> db.CountryInfo.find().sort(["IndepYear desc"]).limit(8)
... [output removed]
8 documents in set (0.00 sec)
By default, the limit()
method starts from
the first document in the collection. You can use the
skip()
method to change the starting
document. For example, to ignore the first document and return
the next eight documents matching the condition, pass to the
skip()
method a value of 1.
mysql-py> db.CountryInfo.find().sort(["IndepYear desc"]).limit(8).skip(1)
... [output removed]
8 documents in set (0.00 sec)
The MySQL Reference Manual provides detailed documentation on functions and operators.
See CollectionFindFunction for the full syntax definition.
You can use the modify()
method to update one
or more documents in a collection. The X DevAPI provides
additional methods for use with the modify()
method to:
Set and unset fields within documents.
Append, insert, and delete arrays.
Bind, limit, and sort the documents to be modified.
The modify()
method works by filtering a
collection to include only the documents to be modified and
then applying the operations that you specify to those
documents.
In the following example, the modify()
method uses the search condition to identify the document to
change and then the set()
method replaces
two values within the nested demographics object.
mysql-py> db.CountryInfo.modify("_id = 'SEA'").\
set("demographics", {"LifeExpectancy": 78, "Population": 28})
Query OK, 1 item affected (0.04 sec)
After you modify a document, use the find()
method to verify the change.
To remove content from a document, use the
modify()
and unset()
methods. For example, the following query removes the GNP from
a document that matches the search condition.
mysql-py> db.CountryInfo.modify("Name = 'Sealand'").unset("GNP")
Query OK, 1 item affected (0.01 sec)
Use the find()
method to verify the change.
mysql-py> db.CountryInfo.find("Name = 'Sealand'")
[
{
"IndepYear": 1967,
"Name": "Sealand",
"_id": "SEA",
"demographics": {
"LifeExpectancy": 78,
"Population": 28
},
"geography": {
"Continent": "Europe",
"Region": "British Islands",
"SurfaceArea": 193
},
"government": {
"GovernmentForm": "Monarchy",
"HeadOfState": "Michael Bates"
}
}
]
1 document in set (0.00 sec)
To append an element to an array field, or insert, or delete
elements in an array, use the
arrayAppend()
,
arrayInsert()
, or
arrayDelete()
methods. The following
examples modify the CountryInfo collection to enable tracking
of international airports.
The first example uses the modify()
and
set()
methods to create a new Airports
field in all documents.
Use care when you modify documents without specifying a search condition. This action will modify all documents in the collection.
mysql-py> db.CountryInfo.modify().set("Airports", [])
Query OK, 240 items affected (0.07 sec)
With the Airports field added, the next example uses the
arrayAppend()
method to add a new airport
to one of the documents. $.Airports in
the following example represents the Airports field of the
current document.
mysql-py> db.CountryInfo.modify("Name = 'France'").arrayAppend("$.Airports", "ORY")
Query OK, 1 item affected (0.02 sec)
Use db.CountryInfo.find("Name =
'France'")
to see the change.
To insert an element at a different position in the array, use
the arrayInsert()
method to specify which
index to insert in the path expression. In this case, the
index is 0, or the first element in the array.
mysql-py> db.CountryInfo.modify("Name = 'France'").arrayInsert("$.Airports[0]", "CDG")
Query OK, 1 item affected (0.04 sec)
To delete an element from the array, you must pass to the
arrayDelete()
method the index of the
element to be deleted.
mysql-py> db.CountryInfo.modify("Name = 'France'").arrayDelete("$.Airports[1]")
Query OK, 1 item affected (0.03 sec)
The MySQL Reference Manual provides instructions to help you search for and modify JSON values.
See CollectionModifyFunction for the full syntax definition.
You can use the remove()
method to delete
some or all documents from a collection in a database. The
X DevAPI provides additional methods for use with the
remove()
method to filter and sort the
documents to be removed.
The example that follows passes a search condition to the
remove()
method. All documents matching the
condition will be removed from the CountryInfo collection. In
this example, one document matches the condition.
mysql-py> db.CountryInfo.remove("_id = 'SEA'")
Query OK, 1 item affected (0.02 sec)
To remove the first document in the CountryInfo collection,
use the limit()
method with a value of 1.
mysql-py> db.CountryInfo.remove().limit(1)
Query OK, 1 item affected (0.03 sec)
The following example removes the last document in the CountryInfo collection by country name.
mysql-py> db.CountryInfo.remove().sort(["Name desc"]).limit(1)
Query OK, 1 item affected (0.02 sec)
You can remove all documents in a collection. To do so, use
the remove()
method without specifying a
search condition.
Use care when you remove documents without specifying a search condition. This action will delete all documents from the collection.
See CollectionRemoveFunction for the full syntax definition.
See Section 3.5.2, “Import Database Sample”
for instructions to recreate the
world_x
database.
Indexes are used to find documents with specific field values quickly. Without an index, MySQL must begin with the first document and then read through the entire collection to find the relevant fields. The larger the collection, the more this costs. If a collection is large and queries on a specific field are common, then consider creating an index on a specific field inside a document.
For example, the following query will perform better with an index:
mysql-js> db.CountryInfo.find("demographics.Population < 100")
...[output removed]
8 documents in set (0.00 sec)
The createIndex()
method creates an index
that you can define as nonunique or unique. Use the
field()
method to chain the fields that
should be indexed. The execute()
method is
required to create or drop an index.
In MySQL, the _id
field is equivalent to a
primary key by default.
To create a nonunique index, pass to the
createIndex()
method an index name.
Duplicate index names are prohibited.
In the following example, the first parameter of the
field()
method specifies the Population
field inside the demographics object and the next parameter
indicates that the field should be indexed as an Integer
numeric value. The last parameter indicates whether the field
should require the NOT NULL constraint. If the value is
False
, the field can contain
NULL
values.
mysql-js> db.CountryInfo.createIndex("pop").\
field("demographics.Population", "INTEGER", False).execute()
Query OK (0.04 sec)
To create a unique index, pass to the
createIndex()
method an index name and the
mysqlx.IndexType.Unique
type. The following
statement imports the mysqlx module, which is required to
specify an index type:
mysql-js> import mysqlx
Country "Name"
is another common field in
the CountryInfo collection to index. In the following example,
"Text(40)"
represents the number of
characters to index and True
indicates that
the field cannot contain any NULL
values.
mysql-js> db.CountryInfo.createIndex("name", mysqlx.IndexType.Unique).\
field("Name", "TEXT(40)", True).execute()
Query OK (0.04 sec)
To drop an index, pass to the dropIndex()
method the name of the index to drop. For example, you can
drop the “pop” index as follows:
mysql-js> db.CountryInfo.dropIndex("pop").execute()
Query OK (0.58 sec)
See Collection Index Management Functions for the full syntax definition.
You can use MySQL Shell to manipulate not just JSON documents, but also relational tables.
In MySQL, each relational table is associated with a particular
storage engine. The examples in this section use
InnoDB
tables in the
world_x
database.
To show the value that is assigned to the schema variable, type
db
.
mysql-py> db
<Schema:world_x>
If the schema value is not the Schema:world_x
database, then set the db
variable as follows:
mysql-py> \use world_x
Schema `world_x` accessible through db.
To display all relational tables in the world_x
database, use the getTables()
method on the
schema object.
mysql-py> db.getTables()
{
"City": <Table:City>,
"Country": <Table:Country>,
"CountryLanguage": <Table:CountryLanguage>
}
Basic operations scoped by tables include:
Operation form | Description |
---|---|
db. | The insert() method inserts one or more records into the named table. |
db. | The select() method returns some or all records in the named table. |
db. | The update() method updates records in the named table. |
db. | The delete() method deletes one or more records from the named table. |
See Working with Relational Tables for a general overview.
CRUD EBNF Definitions provides a complete list of operations.
See Section 3.5.2, “Import Database Sample” for
instructions on setting up the world_x
database sample.
You can use the insert()
method with the
values()
method to insert records into an
existing relational table. The insert()
method accepts individual columns or all columns in the table.
Use one or more values()
methods to specify
the values to be inserted.
To insert a complete record, pass to the
insert()
method all columns in the table.
Then pass to the values()
method one value
for each column. For example, to add a new record to the City
table in the world_x
database, insert the
following record and press Enter twice.
mysql-py> db.City.insert("ID", "Name", "CountryCode", "District", "Info").\
values(None, "Olympia", "USA", "Washington", '{"Population": 5000}')
Query OK, 1 item affected (0.01 sec)
The City table has five columns: ID, Name, CountryCode, District, and Info. Each value must match the data type of the column it represents.
The following example inserts values into the ID, Name, and CountryCode columns of the City table.
mysql-py> db.City.insert("ID", "Name", "CountryCode").\
values(None, "Little Falls", "USA").values(None, "Happy Valley", "USA")
Query OK, 2 item affected (0.03 sec)
When you specify columns using the insert()
method, the number of values must match the number of columns.
In the previous example, you must supply three values to match
the three columns specified.
See TableInsertFunction for the full syntax definition.
You can use the select()
method to query for
and return records from a table in a database. The
X DevAPI provides additional methods to use with the
select()
method to filter and sort the
returned records.
MySQL provides the following operators to specify search
conditions: OR
(||
),
AND
(&&
),
XOR
, IS
,
NOT
, BETWEEN
,
IN
, LIKE
,
!=
, <>
,
>
, >=
,
<
, <=
,
&
, |
,
<<
, >>
,
+
, -
,
*
, /
,
~
, and %
.
To issue a query that returns all records from an existing
table, use the select()
method without
specifying search conditions. The following example selects
all records from the City table in the
world_x
database.
Limit the use of the empty select()
method to interactive statements. Always use explicit
column-name selections in your application code.
mysql-py> db.City.select()
+------+------------+-------------+------------+-------------------------+
| ID | Name | CountryCode | District | Info |
+------+------------+-------------+------------+-------------------------+
| 1 | Kabul | AFG | Kabol |{"Population": 1780000} |
| 2 | Qandahar | AFG | Qandahar |{"Population": 237500} |
| 3 | Herat | AFG | Herat |{"Population": 186800} |
... ... ... ... ...
| 4079 | Rafah | PSE | Rafah |{"Population": 92020} |
+------+------- ----+-------------+------------+-------------------------+
4082 rows in set (0.01 sec)
An empty set (no matching records) returns the following information:
Empty set (0.00 sec)
To issue a query that returns a set of table columns, use the
select()
method and specify the columns to
return between square brackets. This query returns the Name
and CountryCode columns from the City table.
mysql-py> db.City.select(["Name", "CountryCode"])
+-------------------+-------------+
| Name | CountryCode |
+-------------------+-------------+
| Kabul | AFG |
| Qandahar | AFG |
| Herat | AFG |
| Mazar-e-Sharif | AFG |
| Amsterdam | NLD |
... ...
| Rafah | PSE |
| Olympia | USA |
| Little Falls | USA |
| Happy Valley | USA |
+-------------------+-------------+
4082 rows in set (0.00 sec)
To issue a query that returns rows matching specific search
conditions, use the where()
method to
include those conditions. For example, the following example
returns the names and country codes of the cities that start
with the letter Z.
mysql-py> db.City.select(["Name", "CountryCode"]).where("Name like 'Z%'")
+-------------------+-------------+
| Name | CountryCode |
+-------------------+-------------+
| Zaanstad | NLD |
| Zoetermeer | NLD |
| Zwolle | NLD |
| Zenica | BIH |
| Zagazig | EGY |
| Zaragoza | ESP |
| Zamboanga | PHL |
| Zahedan | IRN |
| Zanjan | IRN |
| Zabol | IRN |
| Zama | JPN |
| Zhezqazghan | KAZ |
| Zhengzhou | CHN |
... ...
| Zeleznogorsk | RUS |
+-------------------+-------------+
59 rows in set (0.00 sec)
You can separate a value from the search condition by using
the bind()
method. For example, instead of
using "Name = 'Z%' " as the condition, substitute a named
placeholder consisting of a colon followed by a name that
begins with a letter, such as name. Then
include the placeholder and value in the
bind()
method as follows:
mysql-py> db.City.select(["Name", "CountryCode"]).\
where("Name like :name").bind("name", "Z%")
Within a program, binding enables you to specify placeholders in your expressions, which are filled in with values before execution and can benefit from automatic escaping, as appropriate.
Always use binding to sanitize input. Avoid introducing values in queries using string concatenation, which can produce invalid input and, in some cases, can cause security issues.
To issue a query using the AND
operator, add the operator between search conditions in the
where()
method.
mysql-py> db.City.select(["Name", "CountryCode"]).\
where("Name like 'Z%' and CountryCode = 'CHN'")
+----------------+-------------+
| Name | CountryCode |
+----------------+-------------+
| Zhengzhou | CHN |
| Zibo | CHN |
| Zhangjiakou | CHN |
| Zhuzhou | CHN |
| Zhangjiang | CHN |
| Zigong | CHN |
| Zaozhuang | CHN |
... ...
| Zhangjiagang | CHN |
+----------------+-------------+
22 rows in set (0.01 sec)
To specify multiple conditional operators, you can enclose the
search conditions in parenthesis to change the operator
precedence. The following example demonstrates the placement
of AND
and
OR
operators.
mysql-py> db.City.select(["Name", "CountryCode"]).\
where("Name like 'Z%' and (CountryCode = 'CHN' or CountryCode = 'RUS')")
+-------------------+-------------+
| Name | CountryCode |
+-------------------+-------------+
| Zhengzhou | CHN |
| Zibo | CHN |
| Zhangjiakou | CHN |
| Zhuzhou | CHN |
... ...
| Zeleznogorsk | RUS |
+-------------------+-------------+
29 rows in set (0.01 sec)
You can apply the limit()
,
orderBy()
, and offSet()
methods to manage the number and order of records returned by
the select()
method.
To specify the number of records included in a result set,
append the limit()
method with a value to
the select()
method. For example, the
following query returns the first five records in the Country
table.
mysql-py> db.Country.select(["Code", "Name"]).limit(5)
+------+-------------+
| Code | Name |
+------+-------------+
| ABW | Aruba |
| AFG | Afghanistan |
| AGO | Angola |
| AIA | Anguilla |
| ALB | Albania |
+------+-------------+
5 rows in set (0.00 sec)
To specify an order for the results, append the
orderBy()
method to the
select()
method. Pass to the
orderBy()
method a list of one or more
columns to sort by and, optionally, the descending
(desc
) or ascending
(asc
) attribute as appropriate. Ascending
order is the default order type.
For example, the following query sorts all records by the Name column and then returns the first three records in descending order .
mysql-py> db.Country.select(["Code", "Name"]).orderBy(["Name desc"]).limit(3)
+------+------------+
| Code | Name |
+------+------------+
| ZWE | Zimbabwe |
| ZMB | Zambia |
| YUG | Yugoslavia |
+------+------------+
3 rows in set (0.00 sec)
By default, the limit()
method starts from
the first record in the table. You can use the
offset()
method to change the starting
record. For example, to ignore the first record and return the
next three records matching the condition, pass to the
offset()
method a value of 1.
mysql-py> db.Country.select(["Code", "Name"]).orderBy(["Name desc"]).limit(3).offset(1)
+------+------------+
| Code | Name |
+------+------------+
| ZMB | Zambia |
| YUG | Yugoslavia |
| YEM | Yemen |
+------+------------+
3 rows in set (0.00 sec)
The MySQL Reference Manual provides detailed documentation on functions and operators.
See TableSelectFunction for the full syntax definition.
You can use the update()
method to modify one
or more records in a table. The update()
method works by filtering a query to include only the records to
be updated and then applying the operations you specify to those
records.
To replace a city name in the City table, pass to the
set()
method the new city name. Then, pass to
the where()
method the city name to locate
and replace. The following example replaces the city Peking with
Beijing.
mysql-py> db.City.update().set("Name", "Beijing").where("Name = 'Peking'")
Query OK, 1 item affected (0.04 sec)
Use the select()
method to verify the change.
mysql-py> db.City.select(["ID", "Name", "CountryCode", "District", "Info"]).where("Name = 'Beijing'")
+------+-----------+-------------+----------+-----------------------------+
| ID | Name | CountryCode | District | Info |
+------+-----------+-------------+----------+-----------------------------+
| 1891 | Beijing | CHN | Peking | {"Population": 7472000} |
+------+-----------+-------------+----------+-----------------------------+
1 row in set (0.00 sec)
See TableUpdateFunction for the full syntax definition.
You can use the delete()
method to remove
some or all records from a table in a database. The
X DevAPI provides additional methods to use with the
delete()
method to filter and order the
records to be deleted.
The example that follows passes search conditions to the
delete()
method. All records matching the
condition will be deleted from the City table. In this
example, one record matches the condition.
mysql-py> db.City.delete().where("Name = 'Olympia'")
Query OK, 1 item affected (0.01 sec)
To delete the first record in the City table, use the
limit()
method with a value of 1.
mysql-py> db.City.delete().limit(1)
Query OK, 1 item affected (0.02 sec)
You can delete all records in a table. To do so, use the
delete()
method without specifying a search
condition.
Use care when you delete records without specifying a search condition. This action will delete all records from the table.
See TableDeleteFunction for the full syntax definition.
See Section 3.5.2, “Import Database Sample”
for instructions to recreate the
world_x
database.
In MySQL, a table may contain traditional relational data, JSON
values, or both. You can combine traditional data with JSON
documents by storing the documents in columns having a native
JSON
data type.
Examples in this section use the City table in the
world_x
database.
The City table has five columns (or fields).
+---------------+------------+-------+-------+---------+------------------+ | Field | Type | Null | Key | Default | Extra | +---------------+------------+-------+-------+---------+------------------+ | ID | int(11) | NO | PRI | null | auto_increment | | Name | char(35) | NO | | | | | CountryCode | char(3) | NO | | | | | District | char(20) | NO | | | | | Info | json | YES | | null | | +---------------+------------+-------+-------+---------+------------------+
To insert a document into the column of a table, pass to the
values()
method a well-formed JSON document
in the correct order. In the following example, a document is
passed as the final value to be inserted into the Info column.
mysql-py> db.City.insert().\
values(None, "San Francisco", "USA", "California", '{"Population":830000}')
Query OK, 1 item affected (0.01 sec)
You can issue a query with a search condition that evaluates document values in the expression.
mysql-py> db.City.select(["ID", "Name", "CountryCode", "District", "Info"]).\
where("CountryCode = :country and Info->'$.Population' > 1000000").\
bind('country', 'USA')
+------+----------------+-------------+----------------+-----------------------------+
| ID | Name | CountryCode | District | Info |
+------+----------------+-------------+----------------+-----------------------------+
| 3793 | New York | USA | New York | {"Population": 8008278} |
| 3794 | Los Angeles | USA | California | {"Population": 3694820} |
| 3795 | Chicago | USA | Illinois | {"Population": 2896016} |
| 3796 | Houston | USA | Texas | {"Population": 1953631} |
| 3797 | Philadelphia | USA | Pennsylvania | {"Population": 1517550} |
| 3798 | Phoenix | USA | Arizona | {"Population": 1321045} |
| 3799 | San Diego | USA | California | {"Population": 1223400} |
| 3800 | Dallas | USA | Texas | {"Population": 1188580} |
| 3801 | San Antonio | USA | Texas | {"Population": 1144646} |
+------+----------------+-------------+----------------+-----------------------------+
9 rows in set (0.01 sec)
See Working with Relational Tables and Documents for a general overview.
See Section 12.6, “The JSON Data Type” for a detailed description of the data type.
This section explains how to use MySQL Shell to script a server using MySQL for Visual Studio.
MySQL for Visual Studio provides access to MySQL objects and data without forcing developers to leave Visual Studio. Designed and developed as a Visual Studio package, MySQL for Visual Studio integrates directly into Server Explorer providing a seamless experience for setting up new connections and working with database objects.
The following MySQL for Visual Studio features are available as of version 2.0.2:
JavaScript and Python code editors, where scripts in those languages can be executed to query data from a MySQL database.
Better integration with the Server Explorer to open MySQL, JavaScript, and Python code editors directly from a connected MySQL instance.
A newer user interface for displaying query results, where different views are presented from result sets returned by a MySQL Server like:
Multiple tabs for each result set returned by an executed query.
Results view, where the information can be seen in grid, tree, or text representation for JSON results.
Field types view, where information about the columns of a result set is shown, such as names, data types, character sets, and more.
Query statistics view, displaying information about the executed query such as execution times, processed rows, index and temporary tables usage, and more.
Execution plan view, displaying an explanation of the query execution done internally by the MySQL Server.
The requirements are MySQL for Visual Studio 2.0.2 or higher, and Visual Studio 2010 or higher. X DevAPI support requires MySQL Server 5.7.12 or higher with the X plugin enabled.
Before opening a code editor that can execute queries against a MySQL server, a connection needs to be established:
Open the Server Explorer pane through the View menu, or with Control + W, K.
Right-click on the Data Connections node, select Add Connection....
In the Add Connection dialog, make sure the MySQL Data Provider is being used and fill in all the information.
To enter the port number, click
and set the Port among the list of connection properties.Click
to ensure you have a valid connection, then click .Right-click your newly created connection, select
and then the language for the code editor you want to open.For existing MySQL connections, to create a new editor you need only to do the last step.
The MySQL script editors have a toolbar at the top where information about the session is displayed, along with the actions that can be executed.
Note the first two buttons in the toolbar represent a way to connect or disconnect from a MySQL server. If the editor was opened from the Server Explorer, the connection will be already established for the new editor window.
The third button is the
button, the script contained in the editor window is executed by clicking it and results from the script execution are displayed below the script window.Some commands in the MySQL Shell can be executed without appending execute() while in interactive mode. In MySQL for Visual Studio, these commands do require execute(). In other words, append ".execute()" to execute commands.
X Plugin extends MySQL Server to be able to function as a document store. Running X Plugin enables MySQL Server to communicate with clients using the X Protocol, which is designed to expose the ACID compliant storage abilities of MySQL as a document store. Documents are stored in JSON format and enable schema-less storage. Using the X DevAPI you can use a NoSQL-like syntax to execute Create, Read, Update, Delete (CRUD) operations against these documents.
This section explains how to configure and monitor the X Plugin in MySQL Server.
This section describes the available command-line options and system variables which configure MySQL Shell.
This table provides an overview of the command-line options, and system and status variables provided by X Plugin.
Table 3.1 X Plugin Option and Variable Reference
The following system variables configure X Plugin:
Command-Line Format | --mysqlx_port=# | ||
System Variable | Name | mysqlx_port | |
Variable Scope | Global | ||
Dynamic Variable | No | ||
Permitted Values | Type | integer | |
Default | 33060 | ||
Min Value | 1 | ||
Max Value | 65535 |
Specifies the port where the X Plugin listens for connections. This option is only read at start up, therefore to change it on a running server requires a restart.
--mysqlx_connect_timeout[=
value
]
Command-Line Format | --mysqlx_connect_timeout=# | ||
System Variable | Name | mysqlx_connect_timeout | |
Variable Scope | Global | ||
Dynamic Variable | Yes | ||
Permitted Values | Type | integer | |
Default | 30 | ||
Min Value | 1 | ||
Max Value | 18446744073709551615 |
Number of seconds to wait for the first packet to be received from newly connected clients. This option is dynamically changeable.
mysqlx_idle_worker_thread_timeout[=
value
]
Command-Line Format | --mysqlx_idle_worker_thread_timeout=# | ||
Permitted Values | Type | integer | |
Default | 60 | ||
Min Value | 0 | ||
Max Value | 18446744073709551615 |
Time in seconds after which an idle worker thread is terminated.
mysqlx_max_allowed_packet[=
value
]
Command-Line Format | --mysqlx_max_allowed_packet=# | ||
Permitted Values | Type | integer | |
Default | 1048576 | ||
Min Value | 0 | ||
Max Value | 18446744073709551615 |
Maxmum size of a network packet that X Plugin can process. This option is dynamically changeable.
mysqlx_max_connections[=
value
]
Command-Line Format | --mysqlx_max_connections=# | ||
System Variable | Name | mysqlx_max_connections | |
Variable Scope | Global | ||
Dynamic Variable | Yes | ||
Permitted Values | Type | integer | |
Default | 100 | ||
Min Value | 1 | ||
Max Value | 18446744073709551615 |
Maximum number of concurrent client connections the X Plugin can accept. This option is dynamically changeable. When modifying this variable, if the new value is smaller than the current number of connections, the new limit is only taken into account for new connections.
mysqlx_min_worker_threads[=
value
]
Command-Line Format | --mysqlx_min_worker_threads=# | ||
Permitted Values | Type | integer | |
Default | 2 | ||
Min Value | 1 | ||
Max Value | 18446744073709551615 |
The minimum number of worker threads the X Plugin uses
for handling client requests. The maximum number of worker
threads is limited implicitly by
--mysqlx_max_connections
.
This option is dynamically changeable.
Command-Line Format | --mysqlx_ssl_ca=file_name | ||
System Variable | Name | mysqlx_ssl_ca | |
Variable Scope | Global | ||
Dynamic Variable | No | ||
Permitted Values | Type | file name |
The equivalent of ssl_ca
for X Plugin, see that variable for more information.
Command-Line Format | --mysqlx_ssl_capath=dir_name | ||
System Variable | Name | mysqlx_ssl_capath | |
Variable Scope | Global | ||
Dynamic Variable | No | ||
Permitted Values | Type | directory name |
The equivalent of
ssl_capath
for
X Plugin, see that variable for more information.
Command-Line Format | --mysqlx_ssl_cert | ||
System Variable | Name | mysqlx_ssl_key | |
Variable Scope | Global | ||
Dynamic Variable | No | ||
Permitted Values | Type | file name |
The equivalent of ssl_cert
for X Plugin, see that variable for more information.
Command-Line Format | --mysqlx_ssl_cipher=name | ||
Permitted Values | Type | string |
The equivalent of
ssl_cipher
for
X Plugin, see that variable for more information.
Command-Line Format | --mysqlx_ssl_crl=file_name | ||
System Variable | Name | mysqlx_ssl_crl | |
Variable Scope | Global | ||
Dynamic Variable | No | ||
Permitted Values | Type | file name |
The equivalent of ssl_crl
for X Plugin, see that variable for more information.
Command-Line Format | --mysqlx_ssl_crlpath=directory_name | ||
System Variable | Name | mysqlx_ssl_crlpath | |
Variable Scope | Global | ||
Dynamic Variable | No | ||
Permitted Values | Type | directory name |
The equivalent of
ssl_crlpath
for
X Plugin, see that variable for more information.
Command-Line Format | --mysqlx_ssl_key=file_name | ||
System Variable | Name | mysqlx_ssl_key | |
Variable Scope | Global | ||
Dynamic Variable | No | ||
Permitted Values | Type | file name |
The equivalent of ssl_key
for X Plugin, see that variable for more information.
This section describes how to monitor X Plugin. There are two available methods of monitoring, using Performance Schema tables or status variables.
The status variables have the following meanings.
The number of bytes sent through the network.
The number of bytes received through the network.
The number of StmtExecute requests received for the SQL namespace.
The number of StmtExecute requests received for the X Plugin namespace.
The number of create collection statements received.
Mysqlx_stmt_create_collection_index
The number of create collection index statements received.
The number of drop collection statements received.
Mysqlx_stmt_drop_collection_index
The number of drop collection index statements received.
The number of list object statements received.
The number of enable notice statements received.
The number of disable notice statements received.
The number of list notice statements received.
The number of list client statements received.
The number of kill client statements received.
The number of ping statements received.
The number of insert requests received.
The number of update requests received.
The number of delete requests received.
The number of find requests received.
The number of expectation blocks opened.
The number of expectation blocks closed.
The number of rows sent back to clients.
The number of warning notices sent back to clients.
The number of other types of notices sent back to clients.
The current SSL cipher (empty for non-SSL connections).
A list of possible SSL ciphers (empty for non-SSL connections).
The certificate verification depth for SSL connection.
The certificate verification mode for SSL connection.
The name of the protocol used for the connection ssl.
The number of sessions that have been opened.
The number of sessions that have been closed.
The number of sessions that have closed with a fatal error.
The number of errors during initialisation.
The number of session attempts which have been accepted.
The number of session attempts which have been rejected.
The number of sessions which have been killed.
The number of connections which have been closed.
The number of connections which have been accepted.
The number of connections which have been rejected.
Mysqlx_connection_accept_errors
The number of connections which have caused accept errors.
The number of connections which have caused errors.
The number of worker threads available.
The number of worker threads currently used.
If SSL is active.
The certificate verification depth limit currently set in ctx.
The certificate verification mode currently set in ctx.
The number of successful SSL connections to the server.
The number of accepted SSL connections.
The last date for which the SSL certificate is valid.
The first date for which the SSL certificate is valid.
Mysqlx_ssl_accept_renegotiates
The number of negotiations needed to establish the connection.
The number of errors sent to clients.
This section provides user documentation for MySQL Shell, which enables you to prototype code using the X DevAPI to communicate with a MySQL Server running the X Plugin. The X Plugin is a new MySQL Server feature available with MySQL Server 5.7.12 and higher.
MySQL Shell is an advanced command-line client and code editor for the MySQL Server. In addition to SQL, MySQL Shell also offers scripting capabilities for JavaScript and Python. When MySQL Shell is connected to the MySQL Server through the X Protocol, the X DevAPI can be used to work with both relational and document data.
The following features are available in MySQL Shell.
MySQL Shell provides an interactive code execution mode, where you type code at the MySQL Shell prompt and each entered statement is processed, with the result of the processing printed onscreen.
MySQL Shell processes code in the following languages: JavaScript, Python and SQL. Any entered code is processed as one of these languages, based on the language that is currently active. There are also specific commands that are treated as “shell commands” which enable you to configure MySQL Shell or retrieve information. For more information see Section 3.8.4.1, “MySQL Shell Commands”.
In addition to the interactive execution of code, MySQL Shell can also take code from different sources and process it. This method of processing code in a non-interactive way is called Batch Execution.
As batch execution mode is intended for script processing of a
single language, it is limited to having minimal non-formatted
output and disabling the execution of commands. To avoid these
limitations, use the --interactive
command-line option, which tells MySQL Shell to execute the
input as if it were an interactive session. In this mode the input
is processed line by line just as if each
line were typed in an interactive session. For more information
see Section 3.8.3.5, “Batch Mode Made Interactive”.
MySQL Shell provides output in different formats depending on how it is used: Tabbed, Table and JSON. For more information see Section 3.8.3.3, “Output Formats”.
Multiple-line code can be written using a command, enabling MySQL Shell to cache multiple lines and then execute them as a single statement. For more information see Section 3.8.3.5.1, “Multiple-line Support”.
MySQL Shell maintains a list of connection data for different servers. You can connect to a server using these stored sessions. The list of stored sessions can be edited. See Section 3.8.5, “Stored Sessions” for more information.
MySQL Shell can be configured to log information about the execution process. For more information see Section 3.8.6, “MySQL Shell Application Log”.
Code written in MySQL Shell uses the X DevAPI, provided for Python and JavaScript. For general information, see X DevAPI User Guide.
MySQL Shell is designed to provide an integrated command-line client for all MySQL products which support X Protocol. The development features of MySQL Shell are designed for sessions using the X Protocol. MySQL Shell can also connect to MySQL Servers that do not support the X Protocol using the legacy MySQL Protocol. A minimal set of features from the X DevAPI are available for sessions created using the legacy MySQL protocol.
Interaction with a MySQL Server is done through a Session object.
For Python and JavaScript, a Session can be created through the
getSession
and
getNodeSession
functions of the mysqlx module.
If a session is created in JavaScript mode using any of these
methods, it is available only in JavaScript mode. The same happens
if the session is created in Python mode. None of these sessions
can be used in SQL mode.
For SQL Mode, the concept of Global Session is supported by the
MySQL Shell. A Global Session is created when the connection
information is passed to MySQL Shell using command-line options,
or by using the \connect
command.
The Global Session is used to execute statements in SQL mode and
the same session is available in both Python or JavaScript modes.
When a Global Session is created, a variable called
session
is set in the scripting languages, so
you can execute code in the different languages by switching the
active mode.
For more information, see Section 3.8.2.1, “MySQL Shell Sessions”.
This section describes how to get started with MySQL Shell. This section assumes you have a MySQL Server running X Plugin and that you have installed MySQL Shell, see Section 3.3, “Setting Up MySQL as a Document Store”.
This section explains the different types of sessions in MySQL Shell and how to create and configure them.
MySQL Shell is a unified interface to operate MySQL Server through scripting languages such as JavaScript or Python. To maintain compatibility with previous versions, SQL can also be executed in certain modes. A connection to a MySQL server is required. In MySQL Shell these connections are handled by a Session object.
The following different types of Session objects are available:
XSession: Use this session type for new application development. It offers the best integration with MySQL Server, and therefore, it is used by default. SQL execution is not supported and therefore it is not compatible with MySQL Shell's SQL Mode.
Node Session: Use this session type for SQL execution on a MySQL Server with the X Protocol enabled. SQL execution is available with this session type, therefore it can be used in MySQL Shell's SQL Mode.
This session type should only be used when connecting directly to an X Protocol enabled MySQL Server.
Classic Session Use this session type to interact with MySQL Servers that do not have the X Protocol enabled. SQL execution is available with this session type, therefore it can be used in MySQL Shell's SQL Mode.
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.
MySQL Shell creates an XSession object by default. To choose which type of session should be created, use one of these options:
For more information, see Section 3.8.2.2.1, “Connecting using a URI String” and Section 3.8.2.2.2, “Connecting using Individual Parameters”.
MySQL Shell can be configured to connect to a MySQL Server
running X Plugin using command-line options at start up or
from MySQL Shell itself. The address of the MySQL Server can be
specified using individual parameters, such as user, hostname and
port, or using a Uniform Resource Identifier (URI) in the format
user@host:port/schema
, such as
mike@myserver:33060/testDB
. The following
sections describe these methods.
Regardless of the method you choose to connect it is important to understand how passwords are handled by MySQL Shell:
By default connections are assumed to require a password. The
password is requested at the login prompt. To specify a
password-less account use the
--password
option, or use a
:
after the user
in a URI.
If you do not specify parameters for a connection the following defaults are used:
user defaults to the current system user name
host defaults to localhost
port defaults to the X Plugin port 33060 when using an X Session, and port 3306 when using a Classic session
MySQL Shell connections using X Protocol
always use TCP, using Linux sockets is not
supported. MySQL Shell connections using MySQL Protocol can use
Linux sockets by specifying the
--socket
command-line option.
You configure the MySQL Server which MySQL Shell connects to
by passing the connection data in string format using the
--uri
command-line option.
Use the following format:
[dbuser
[:[dbpassword
]]@]host
[:port
][/schema
]
Descriptions of these options:
dbuser
: specifies the MySQL user
account to be used for the authentication process.
dbpassword
: specifies the dbuser
password to be used for the authentication process.
Storing the password in the URI is not recommended.
host
: specifies the host to which
the session object connects. If not specified,
localhost is used by default.
port
: specifies which port the
target MySQL server is listening on for the connection. If
not specified, 33060 is used by default for the
X Protocol enabled sessions, and 3306 is the default
for traditional MySQL protocol sessions.
schema
: Indicates the database to
be set as default when the session is established.
If no password is specified using the URI, which is recommended, then the password is prompted for. The following examples show how to use these command-line options:
Connect with a Node Session at port 33065.
shell> mysqlsh --uri user
@localhost:33065 --node
Connect with a Classic Session.
shell> mysqlsh --uri user
@localhost --classic
Although using a password-less account is not recommended, you
can specify a user without a password using a
:
after the user name, for example:
shell> mysqlsh --uri user
:@localhost
In addition to specifying a URI manually, you can use a stored session. See Section 3.8.5, “Stored Sessions” for more information.
In addition to specifying connection parameters using a URI, it is also possible to define the connection data using separate parameters for each value.
Use the following parameters:
--dbuser
(-u
) value
--dbpassword
value
--host
(-h
)
value
--port
(-P
)
value
--schema
(-D
) value
--session-type
value
.
Removed in version 1.0.4.
--password
(-p
)
The first 5 parameters match the tokens used in the URI format described at Section 3.8.2.2.1, “Connecting using a URI String”.
The --password
parameter
indicates the user should connect without a
password.
For consistency, the following aliases are supported for some parameters:
--password
is equivalent to
--dbpassword
--database
is equivalent to
--schema
Attempt to establish an XSession with a specified user at port 33065.
shell> mysqlsh -u user
-h localhost -P 33065
Attempt to establish a Classic Session with a specified user.
shell> mysqlsh -u user
-h localhost --classic
Attempt to establish a Node Session with a specified user.
shell> mysqlsh --node -u user
-h localhost
Using SSL is possible when connecting to an SSL enabled MySQL server.
To configure an SSL connection, use the following command-line options:
--ssl
: This enables or disables
connections through SSL. If set to 0, the other SSL
command-line options are ignored.
--ssl-ca=
:
The path to a file in PEM format that contains a list of
trusted SSL certificate authorities.
filename
--ssl-cert=
:
The name of the SSL certificate file in PEM format to use
for establishing a secure connection.
filename
--ssl-key=
:
The name of the SSL key file in PEM format to use for
establishing a secure connection.
filename
The --ssl
option is assumed to be 1 (enabled)
if the other SSL options are set.
When the --uri
option is
specified in combination with some of the individual parameters,
the address specified by the
--uri
option is used as the base
connection data and the values provided using individual
parameters override the corresponding value from the URI. If the
--user
option is used, it would
replace any user specified as part of a URI.
For example to establish an XSession and override
user
from the URI:
shell> mysqlsh --uri user
@localhost:33065 --user otheruser
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 following Shell Commands:
\connect URI
: Creates an XSession.
\connect -n URI
: Creates a Node Session.
\connect -c URI
: Creates a Classic
Session.
Configure the connection using the URI parameter, which follows
the same syntax as for the --uri
command-line option. For additional information, see
Section 3.8.2.2.1, “Connecting using a URI String”.
For example:
mysql-js> \connect root@localhost
Creating XSession to root@localhost...
Enter password: ****
No default schema selected.
mysql-js>
To establish an SSL connection, the URI parameter passed to the connect shell commands must include the SSL information as URL parameters. For example:
mysql-js> \connect root@localhost?ssl_ca=/path/to/ca/file&\
ssl_cert=/path/to/cert/file&ssl_key=/path/to/key/file
Creating XSession to root@localhost...
Enter password: ****
No default schema selected.
mysql-js>
When a connection is made using the command-line options or by using any of the shell commands, a global session object is created. This session is global because once created, it can be used in any of the MySQL Shell execution modes.
Any global session object is available in JavaScript or Python modes because a variable called session holds a reference to it.
In SQL mode, both Node and Classic sessions can be used because they both expose SQL execution. In SQL mode an XSession cannot be used.
In addition to the global session object, sessions can be established and assigned to a different variable by using the functions available in the mysql and mysqlx JavaScript and Python modules.
For example, the following functions are provided by these modules:
mysql.getSession(connectionData[, password])
mysqlx.getNodeSession(connectionData[, password])
mysql.getClassicSession(connectionData[, password])
The first of these functions is used to create an XSession which features the most comprehensive development API and supports X Protocol.
The second creates a Node Session which connects to a X Protocol enabled MySQL Server and allows SQL Execution.
The latter returns a Classic Session object which uses the traditional MySQL protocol and has a very limited development API.
connectionData can be either a URI as specified above or a dictionary containing the connection parameters. See Section 3.8.2.2.1, “Connecting using a URI String”.
The following example shows how to create a Node Session using the X Protocol:
mysql-js>var mysqlx=require('mysqlx').mysqlx;
mysql-js>var session=mysqlx.getNodeSession('root@localhost');
mysql-js>print(session)
<NodeSession:root@localhost> mysql-js>
The following example shows how to create a Node Session using the X Protocol so that you can execute SQL:
mysql-js>var mysqlx=require('mysqlx').mysqlx;
mysql-js> var session=mysqlx.getNodeSession({host: 'localhost', dbUser: 'root'}); mysql-js>print(session)
<NodeSession:root@localhost> mysql-js>
The following example shows how to create a Classic Session:
mysql-js>var mysql=require('mysql').mysql;
mysql-js>var session = mysql.getClassicSession('root@localhost:3307');
mysql-js>print(session)
<ClassicSession:root@localhost:3307> mysql-js>
To establish an SSL connection, set the SSL information in the connectionData dictionary. For example:
mysql-js>var mysqlx=require('mysqlx').mysqlx;
mysql-js>var session=mysqlx.getNodeSession({host: 'localhost', dbUser: 'root', dbPassword: 'mypasswd', ssl_ca: "path_to_ca_file", ssl_cert: "path_to_cert_file", ssl_key: "path_to_key_file"});
mysql-js>print(session)
<NodeSession:root@localhost> mysql-js>
MySQL Shell reserves certain variables as global variables, which are assigned to commonly used objects in scripting. This section describes the available global variables and provides examples of working with them. The global variables are:
session
represents the global session if one
has been established.
db
represents a schema if one has been
defined, for example by a URI.
MySQL Shell provides interactive error resolution for common situations related to using the global variables. For example:
Attempting to use an undefined session
global
variable.
Attempting to retrieve an nonexistent schema using
session
.
Attempting to use an undefined db
global
variable.
The global session
variable is set when a
global session is established. When a global session is
established, issuing a session
statement in
MySQL Shell displays the session type and its URI as follows:
mysql-js> session <XSession:root@localhost:33060> mysql-js>
If no global session has been established, MySQL Shell displays the following:
mysql-js> session <Undefined> mysql-js>
If you attempt to use the session
variable when
no global session is established, interactive error resolution
starts and you are prompted to provide the required information to
establish a global session. If the session is successfully
established, it is assigned to the session
variable. The prompts are:
An initial prompt explains that no global session is established and asks if one should be established.
If the you choose to set a global session, the session type is requested.
Either the URI or the alias of a stored session is requested.
If required, a password is requested.
For example:
mysql-js> session.uri The global session is not set, do you want to establish a session? [y/N]: y Please specify the session type: 1) X 2) Node 3) Classic Type: 2 Please specify the MySQL server URI (or $slias): root@localhost Enter password:******* root@localhost:33060 mysql-js>
The global db
variable is set when a global
session is established and a default schema is configured. For
example, using a URI such as
root@localhost/sakila
to establish a global
session connected to the MySQL Server at
localhost
, on port 33060, as the user
root
, assigns the schema
sakila
to the global variable
db
. Once a schema is defined, issuing
db
at the MySQL Shell prompt prints the
schema name as follows:
mysql-js> db <Schema:world_x> mysql-js>
If there is no global session established, the following is displayed:
mysql-js> db <Undefined> mysql-js>
If you attempt to use the db
variable when no
global session has been established, the following error is
displayed:
mysql-js> db.getCollections() LogicError: The db variable is not set, establish a global session first. at (shell):1:2 in db.getCollections() ^
If a global session has been established but you attempt to use an
undefined db
, interactive error resolution
begins and you are prompted to define an active schema by
providing the schema name. If this succeeds the
db
variable is set to the defined schema. For
example:
mysql-js> db.getCollections() The db variable is not set, do you want to set the active schema? [y/N]:y Please specify the schema:world_x [ <Collection:countryinfo> ] mysql-js> db <Schema:world_x> mysql-js>
If you attempt to use session
to retrieve an
nonexistent schema, interactive error resolution provides the
option to create the schema.
mysql-js> var mySchema = session.getSchema('my_test') The schema my_test does not exist, do you want to create it? [y/N]: y mysql-js> mySchema <Schema:my_test> mysql-js>
In all cases, if you do not provide the information required to resolve each situation, a proper result of executing the requested statement on an undefined variable is displayed.
This section explains how code execution works in MySQL Shell.
The default mode of MySQL Shell provides interactive execution of database operations that you type at the command prompt. These operations can be written in JavaScript, Python or SQL depending on the type of session being used. When executed, the results of the operation are displayed on-screen.
As with any other language interpreter, MySQL Shell is very strict regarding syntax. For example, the following JavaScript snippet reads and prints the documents in a collection:
var mysqlx = require('mysqlx').mysqlx; var mySession = mysqlx.getSession('user:pwd@localhost'); var result = mySession.world_x.CountryInfo.find().execute(); var record = result.fetchOne(); while(record){ print(record); record = result.fetchOne(); }
As seen above, the call to find()
is followed
by the execute()
function. CRUD database
commands are only actually executed on the MySQL Server when
execute()
is called. However, when working with
MySQL Shell interactively, execute()
is
implicitly called whenever you press Return
on
a statement. Then the results of the operation are fetched and
displayed on-screen. The rules for when you need to call
execute()
or not are as follows:
When using MySQL Shell in this way, calling
execute()
becomes optional on:
Collection.add()
Collection.find()
Collection.remove()
Collection.modify()
Table.insert()
Table.select()
Table.delete()
Table.update()
NodeSession.sql()
Automatic execution is disabled if the object is assigned to a
variable. In such a case calling execute()
is mandatory to perform the operation.
When a line is processed and the function returns any of the
available Result
objects, the information
contained in the Result object is automatically displayed on
screen. The functions that return a Result object include:
The SQL execution and CRUD operations (listed above)
Transaction handling and drop functions of the session objects in both mysql and mysqlx modules: -
startTransaction()
commit()
rollback()
dropSchema()
dropTable()
dropCollection()
dropView()
ClassicSession.runSql()
Based on the above rules, the statements needed in the MySQL Shell in interactive mode to establish a session, query, and print the documents in a collection are:
mysql-js>var mysqlx = require('mysqlx').mysqlx;
mysql-js>var mySession = mysqlx.getSession('user:pwd@localhost');
No call to execute()
is needed and the Result
object is automatically printed.
mysql-js> mySession.world_x.CountryInfo.find();
As well as interactive code execution, MySQL Shell provides batch code execution from:
A file loaded for processing.
A file containing code that is redirected to the standard input for execution.
Code from a different source that is redirected to the standard input for execution.
For example:
Loading SQL code from a file for batch processing.
shell> mysqlsh --file code.js
Redirecting a file to standard input for execution.
shell> mysqlsh < code.js
Redirecting code to standard input for execution.
shell> echo "show databases;" | mysqlsh --sql --uri root@192.168.1.141:33060
The output of the commands processed on the server can be formatted in different ways. This section details the different available output formats.
The table format is used by default when MySQL Shell is in interactive mode. The output is presented as a formatted table for a better view and to aid analysis.
mysql-sql> select * from sakila.actor limit 3;
+----------+-------------+----------------+----------------------+
| actor_id | first_name | last_name | last_update |
+----------+-------------+----------------+----------------------+
| 1 | PENELOPE | GUINESS | 2006-02-15 4:34:33 |
| 2 | NICK | WAHLBERG | 2006-02-15 4:34:33 |
| 3 | ED | CHASE | 2006-02-15 4:34:33 |
+----------+-------------+----------------+----------------------+
3 rows in set (0.00 sec)
mysql-sql>
To get this output format when running in batch mode, use the
--table
command-line option.
This format is used by default when running MySQL Shell in batch mode, to have better output for automated analysis.
>echo "select * from sakila.actor limit 3;" | mysqlsh --classic --uri root@192.168.1.141:33460
actor_id first_name last_name last_update
1 PENELOPE GUINESS 2006-02-15 4:34:33
2 NICK WAHLBERG 2006-02-15 4:34:33
3 ED CHASE 2006-02-15 4:34:33
MySQL Shell supports the JSON format for output and it is
available both in interactive and batch mode. This output format
can be enabled using the --json
command-line option:
JSON Format in Batch Mode
shell>echo "select * from sakila.actor limit 3;" | mysqlsh --json --sqlc --uri root@192.168.1.141:3306
{"duration":"0.00 sec","info":"","row_count":3,"rows":[[1,"PENELOPE","GUINESS",{"year":2006,"month":1,"day":15,"hour":4,"minute":34,"second":33.0}],[2,"NICK","WAHLBERG",{"year":2006,"month":1,"day":15,"hour":4,"minute":34,"second":33.0}],[3,"ED","CHASE",{"year":2006,"month":1,"day":15,"hour":4,"minute":34,"second":33.0}]],"warning_count":0} shell>echo "select * from sakila.actor limit 3;" | mysqlsh --json=raw --sqlc --uri root@192.168.1.141:3306
{"duration":"0.00 sec","info":"","row_count":3,"rows":[[1,"PENELOPE","GUINESS",{"year":2006,"month":1,"day":15,"hour":4,"minute":34,"second":33.0}],[2,"NICK","WAHLBERG",{"year":2006,"month":1,"day":15,"hour":4,"minute":34,"second":33.0}],[3,"ED","CHASE",{"year":2006,"month":1,"day":15,"hour":4,"minute":34,"second":33.0}]],"warning_count":0} shell>echo "select * from sakila.actor limit 3;" | mysqlsh --json=pretty --sqlc --uri root@192.168.1.141:3306
{ "duration": "0.00 sec", "info": "", "row_count": 3, "rows": [ [ 1, "PENELOPE", "GUINESS", { "year": 2006, "month": 1, "day": 15, "hour": 4, "minute": 34, "second": 33.0 } ], [ 2, "NICK", "WAHLBERG", { "year": 2006, "month": 1, "day": 15, "hour": 4, "minute": 34, "second": 33.0 } ], [ 3, "ED", "CHASE", { "year": 2006, "month": 1, "day": 15, "hour": 4, "minute": 34, "second": 33.0 } ] ], "warning_count": 0 } shell>
JSON Format in Interactive Mode (started with --json=raw)
mysql-sql> select * from sakila.actor limit 3;
{"duration":"0.00 sec","info":"","row_count":3,"rows":[[1,"PENELOPE","GUINESS",{"year":2006,"month":1,"day":15,"hour":4,"minute":34,"second":33.0}],[2,"NICK","WAHLBERG",{"year":2006,"month":1,"day":15,"hour":4,"minute":34,"second":33.0}],[3,"ED","CHASE",{"year":2006,"month":1,"day":15,"hour":4,"minute":34,"second":33.0}]],"warning_count":0}
mysql-sql>
JSON Format in Interactive Mode (started with --json=pretty)
mysql-sql> select * from sakila.actor limit 3;
{
"duration": "0.00 sec",
"info": "",
"row_count": 3,
"rows": [
[
1,
"PENELOPE",
"GUINESS",
{
"year": 2006,
"month": 1,
"day": 15,
"hour": 4,
"minute": 34,
"second": 33.0
}
],
[
2,
"NICK",
"WAHLBERG",
{
"year": 2006,
"month": 1,
"day": 15,
"hour": 4,
"minute": 34,
"second": 33.0
}
],
[
3,
"ED",
"CHASE",
{
"year": 2006,
"month": 1,
"day": 15,
"hour": 4,
"minute": 34,
"second": 33.0
}
]
],
"warning_count": 0
}
mysql-sql>
When an operation is executed, in addition to any results returned, some additional information is available. This includes information such as the number of affected rows, warnings, duration, and so on, when any of these conditions is true:
JSON format is being used for the output
MySQL Shell is running in interactive mode.
MySQL Shell can execute SQL, JavaScript or Python code, but only one language can be active at a time. The active mode determines how the executed statements are processed:
If using SQL mode, statements are processed as SQL which means they are sent to the MySQL server for execution.
If using JavaScript mode, statements are processed as JavaScript code.
If using Python mode, statements are processed as Python code.
When running MySQL Shell in interactive mode, activate a
specific language by entering the commands:
\sql
, \js
,
\py
.
When running MySQL Shell in batch mode, activate a specific
language by passing any of these command-line options:
--js
,
--py
or
--sql
. The default mode if none is
specified is JavaScript.
Use MySQL Shell to execute the content of the file
code.sql
as SQL.
shell> mysqlsh --sql < code.sql
Use MySQL Shell to execute the content of the file
code.js
as JavaScript code.
shell> mysqlsh < code.js
Use MySQL Shell to execute the content of the file
code.py
as Python code.
shell> mysqlsh --py < code.py
This section describes code execution in batch mode.
In batch mode, all the command logic described above is not available, only valid code for the active language can be executed.
When processing SQL code, it is executed statement by statement using the following logic: read/process/print result.
When processing non-SQL code, it is loaded entirely from the input source and executed as a unit.
Use the --interactive
(or
-i
) command-line option to
configure MySQL Shell to process the input source as if it were
being issued in interactive mode; this enables all the features
provided by the Interactive mode to be used in batch processing.
In this case, whatever the source is, it is read line by line and processed using the interactive pipeline.
It is possible to specify statements over multiple lines. When
in Python or JavaScript mode, multiple-line mode is
automatically enabled when a block of statements starts like in
function definitions, if/then statements, for loops, and so on.
In SQL mode multiple line mode starts when the command
\
is issued.
Once multiple-line mode is started, the subsequently entered statements are cached.
For example:
mysql-sql>\
...create procedure get_actors()
...begin
...select first_name from sakila.actor;
...end
... mysql-sql>
This section explains how to configure MySQL Shell using commands executable from the interactive code editor and command-line options. For a description of MySQL Shell command-line options, see Section 5.5.7, “mysqlsh — The MySQL Shell”.
MySQL Shell provides commands which enable you to modify the
execution environment of the code editor, for example to configure
the active programming language or a MySQL Server connection. The
following table lists the commands that are available regardless
of the currently selected language. As commands need to be
available independent of the execution mode,
they start with an escape sequence, the \
character.
Command | Alias/Shortcut | Description |
---|---|---|
|
| Prints help about MySQL Shell commands. |
|
| Exit MySQL Shell. |
| In SQL mode, begin multiple-line mode. Code is cached and executed when an empty line is entered. | |
| Show the current MySQL Shell status. | |
| Switch execution mode to JavaScript. | |
| Switch execution mode to Python. | |
| Switch execution mode to SQL. | |
|
| Connect to a MySQL Server with a URI using an XSession (X Protocol). |
|
|
(Removed in version 1.0.4, use |
|
|
(Removed in version 1.0.4, use |
| Specify the schema to use. | |
|
| Execute a script file using the active language. |
|
| Show any warnings generated by a statement. |
|
| Do not show any warnings generated by a statement. |
|
| Print the connection data for the stored sessions. |
|
|
Save connection data of a session, optionaly use
|
|
|
(Removed in version 1.0.4, see
|
| Removes a stored session. | |
|
(Removed in version 1.0.4, see
|
The \help
command can be used with or without
parameters. When used without parameters a general help is
printed including information about:
Available commands.
Available commands for the active mode.
When used with a parameter, the parameter must be a valid command. If that is the case, help for that specific command is printed including:
Description
Supported aliases if any
Additional help if any
For example:
\help connect
If the parameter is not a valid command, the general help is printed.
The \connect
command is used to connect to a
MySQL Server using an URI. This command creates an
X Protocol connection by default.
For example:
\connect root@localhost:3306
If a password is required you are prompted for it.
Use the -n
option to create a Node session,
using the X Protocol to connect to a single server. For
example:
\connect -n root@localhost:3306
Use the -c
option to create a Classic
session, enabling you to use the MySQL Protocol to issue SQL
commands directly on a server. For example:
\connect -c root@localhost:3306
The \source
command is used to execute code
from a script at a given path. For example:
\source /tmp/mydata.sql
It can be used to execute either SQL, JavaScript or Python code. The code in the file is executed using the active language, so to process SQL code the MySQL Shell must be in SQL mode.
As the code is executed using the active language, executing a script in a different language than the currently selected execution mode language could lead to unexpected results.
The \use
command enables you to choose which
schema is active, for example:
\use schema_name
The \use
command requires a global
development session to be active. If the global development
session is an XSession then the \use
command
only sets db
to the object representing the
schema_name
but does not set a
current schema on the database. If the global development
session is one of NodeSession or ClassicSession the
\
use command sets the current schema to the
specified schema_name
and updates the
db
variable to the object that represents the
selected schema.
This section describes how MySQL Shell stores a persistent list of connection data for sessions, identified by a session name.
There are two approaches to manage and use stored connection data:
Through MySQL Shell commands.
Through a built-in object available for JavaScript and Python.
With these options you can add, update, remove, list and use stored connection data.
The connections are stored as a text file in the MySQL Shell folder, usually found in the user directory.
The file name is stored_sessions.json
In Windows a typical location is:
%APPDATA%\MySQL\mysqlsh\stored_sessions.json
In Unix a typical location is:
~/.mysqlsh/stored_sessions.json
The following commands are used to work with stored sessions within MySQL Shell.
To add connection data for a session use:
\saveconn name [URI]
name
: Mandatory parameter, the
name that is assigned to the stored connection data. Note
that this must be a valid identifier:
Starts with an alphabetic character.
Only contains alphanumeric characters and underscore.
URI
: Optional parameter
containing connection data in URI format. If not specified
and a global session is active, the URI for the global
session is used instead.
-f
: Optional parameter to
force overwriting an existing connection. If an attempt is
made to store a connection, but the provided
name
already exists, an error
occurs. Use this parameter to force storing the connection,
which overrides what was previously stored under the given
session name.
To update the connection data for a specific session name use:
\saveconn -f name
URI
name
: Mandatory parameter,
indicates the connection to be updated.
URI
: Mandatory parameter, contains the
connection data that replaces the connection for the
indicated session name.
To remove a connection use:
\rmconn name
name
: Mandatory parameter that
indicates the connection data to be removed.
Stored connections can be used to create a global session by
issuing a \connect
command. The stored
session is loaded and used to create the global session.
name
When using a stored connection through the connect shell commands, you are prompted for the password if it is missing from the stored connection data.
A built in object is available to manage and use the stored
connections through JavaScript or Python:
shell.storedSessions
To add a new connection use:
shell.storedSessions.add(name, connectionData[, override])
name
: Mandatory parameter, it is
the session name that identifies the connection data. This
must be a valid identifier.
connectionData
: Mandatory parameter, it
contains the connection information and can be either a
string in URI format or a connection data map containing any
of the following values:
host
port
dbUser
dbPassword
schema
ssl_ca
ssl_cert
ssl_key
To store the connection data at least the host and dbUser parameter should be specified, the rest are optional.
override : Optional boolean parameter, used to indicate the desired behavior in case there is a stored connection data associated to the same name. Default value is false.
If override is false and connection data with the same name already exists, an error is generated.
In the same scenario, if the new connection data overrides the previous data and an error is not generated.
To update the connection data for a specific session name use:
shell.storedSessions.update(name, connectionData)
name : Mandatory parameter, it is the name that will identify the connection data. Note that this must be a valid identifier.
connectionData : Mandatory parameter, it contains the connection data and can be either a string in URI format or a connection data map.
To remove a connection use:
shell.storedSessions.remove(name)
name : Mandatory parameter, identifies the connection data to be removed.
When the shell.storedSessions
object is
initialized, it loads the stored session data and creates a
property to access them as
shell.storedSessions.
name
var session = mysqlx.getSession(shell.storedSessions.name)
When used this way, if the connection data has no password it is not requested. It is the developers responsibility to provide the password either using the stored session data or as an additional parameter as follows:
var session = mysqlx.getSession(shell.storedSessions.name, password)
This section explains the application log.
MySQL Shell can be configured to generate an application log file with information about issues of varying severity. You can use this information to verify the state of MySQL Shell while it is running.
The location of the log file is the user configuration path and
the file is named mysqlsh.log
.
On Windows, the default path to the log file is
%APPDATA%\MySQL\mysqlsh\mysqlsh.log
To find the location of %APPDATA%
on your
system, echo it from the comand-line. For example:
C:>echo %APPDATA%
C:\Users\exampleuser\AppData\Roaming
On Windows, the path is determined by the result of gathering the
%APPDATA%
folder specific to that user, and
then appending MySQL\mysqlsh
. Using the above
example, we end up with:
C:\Users\exampleuser\AppData\Roaming\MySQL\mysqlsh\mysqlsh.log
For a machine running Unix, the default path is
~/.mysqlsh/mysqlsh.log
where “~”
represents the user's home directory. The environment variable
HOME
also represents the user's home directory.
Appending .mysqlsh
to the user's home
directory determines the default path to the logs. For example:
C:>echo $HOME
/home/exampleuser shell>less /home/exampleuser/.mysqlsh/mysqlsh.log
These paths can be overridden on all platforms by defining the
environment variable MYSQL_USER_CONFIG_PATH
.
The value of this variable replaces %APPDATA%
in Windows or $HOME
in Unix.
By default, logging is disabled in MySQL Shell. To enable
logging use the --log-level
command-line option when starting MySQL Shell. For example:
shell> mysqlsh --log-level=4
The number assigned to --log-level
controls the level of detail in the log. The following logging
levels are supported:
Log Level | Meaning |
---|---|
1 | None, the default |
2 | Internal Error |
3 | Error |
4 | Warning |
5 | Info |
6 | Debug |
7 | Debug2 |
8 | Debug3 |
The log format is plain text and entries contain a timestamp and description of the problem, along with the log level from the above list. For example:
2016-04-05 22:23:01: Error: Default Domain: (shell):1:8: MySQLError: You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near '' at line 1 (1064) in session.sql("select * from t limit").execute().all();