Search Results
https://dev.mysql.com/doc/ndbapi/en/ndb-ndbdictionary.html
While the preferred method of database object creation and deletion is through the MySQL Server, NdbDictionary also permits the developer to perform these tasks through the NDB API. Tables and indexes created using NdbDictionary cannot be viewed ...
https://dev.mysql.com/doc/ndbapi/en/ndb-ndberror.html
MySQL Error code: This is the corresponding MySQL Server error code. MySQL error codes are not discussed in this document; please see Server Error Message Reference, in the MySQL Manual, for information about these. This section provides ...
https://dev.mysql.com/doc/ndbapi/en/ndb-nodejs-api-mynode.html
To create an instance, use the Node.js require() function with the driver name, like this: var nosql = require("mysql-js"); ConnectionProperties can be used to retrieve or set the connection properties for a given session. This class is used to ...
https://dev.mysql.com/doc/ndbapi/en/overview-terminology.html
More detailed information about LCPs and their behavior can be found in the MySQL Manual; see in particular Defining NDB Cluster Data Nodes. SQL node refers to a mysqld (MySQL Server) process that is connected to the NDB Cluster as an API node. For ... Abstract This section provides a glossary of terms which are unique to the NDB and MGM APIs, or that have a specialized meaning when applied in the context of either or both of these ...
https://dev.mysql.com/doc/x-devapi-userguide/en/connection-option-summary.html
When using an X DevAPI session the following options are available to configure the connection. Figure 2.1 Connection URI ConnectURI1::= 'user' ':' 'password' '@' 'host' ':' 'port' .
https://dev.mysql.com/doc/x-devapi-userguide/en/creating-documents.html
MySQL Connectors that implement X DevAPI aim to implement support for all JSON methods that are native to the Connectors' specific languages. In addition, in some MySQL Connectors the generic DbDoc objects can be used. Once a collection has been ...
https://dev.mysql.com/doc/mysql-monitor/8.0/en/main-queries-reference.html
Note The examples used in this section are taken from the default advisors delivered with your MySQL Enterprise Monitor installation. The following example is used by the Server Has Anonymous Accounts advisor: <class> <namespace>mysql</namespace> ...
https://dev.mysql.com/doc/mysql-monitor/8.0/en/mem-agent-tuning-memory.html
The following are the recommended settings for MySQL Enterprise Monitor Agent: A single agent, with default settings and all advisors enabled, should monitor no more than 10 MySQL instances. If the agent is monitoring more than 10 MySQL instances, ...The agent heap size is defined in the MEM_AGENT_JAVA_OPTS parameter in the setenv.sh/bat ...
https://dev.mysql.com/doc/mysql-monitor/8.0/en/mem-creating-advisors-overview.html
The MySQL functions LEAST(), LOCATE(), ABS(), MOD(), NOW() (returns time since Unix epoch UTC in seconds), UNIX_TIMESTAMP (technically a no-op), and INTERVAL [n] SECOND, MINUTE, HOUR, WEEK, MONTH. Comparisons with MySQL timestamps and datetimes ...
https://dev.mysql.com/doc/mysql-monitor/8.0/en/mem-existing-users.html
The MySQL user: For Agents to report the status of a MySQL server, they connect to a MySQL user with privileges to read required data on that server: SHOW DATABASES, REPLICATION CLIENT, SUPER, CREATE, and SELECT. If you already have such a user on ...