PDF (US Ltr)
- 35.1Mb
PDF (A4)
- 35.2Mb
Man Pages (TGZ)
- 256.4Kb
Man Pages (Zip)
- 361.2Kb
Info (Gzip)
- 3.4Mb
Info (Zip)
- 3.4Mb
Search Results
https://dev.mysql.com/doc/refman/5.7/en/mysql-cluster-replication.html
This section explains how to set up and manage a configuration in which one group of computers operating as an NDB Cluster replicates to a second computer or group of computers. Normal (non-clustered) replication involves a source server (formerly ... NDB Cluster supports asynchronous replication, more usually referred to simply as ...
https://dev.mysql.com/doc/refman/5.7/en/mysql-cluster-security.html
This section discusses security considerations to take into account when setting up and running NDB Cluster. Topics covered in this section include the following: NDB Cluster and network security issues Configuration issues relating to running NDB ...
https://dev.mysql.com/doc/refman/5.7/en/mysql-cluster-system-definition.html
The [system] section is used for parameters applying to the cluster as a whole. More information about these parameters can be found in the following list: ConfigGenerationNumber Version (or later) NDB 7.5.0 Type or units unsigned Default 0 Range 0 ...The Name system parameter is used with MySQL Enterprise Monitor; ConfigGenerationNumber and PrimaryMGMNode are not used in production ...
https://dev.mysql.com/doc/refman/5.7/en/mysql-enterprise-encryption.html
MySQL Enterprise Edition includes a set of encryption functions based on the OpenSSL library that expose OpenSSL capabilities at the SQL level. These functions enable Enterprise applications to perform the following operations: Implement added data ...
https://dev.mysql.com/doc/refman/5.7/en/opengis-geometry-model.html
The set of geometry types proposed by OGC's SQL with Geometry Types environment is based on the OpenGIS Geometry Model. In this model, each geometric object has the following general properties: It is associated with a spatial reference system, ...
https://dev.mysql.com/doc/refman/5.7/en/optimizer-features-to-trace.html
Range optimizer Dynamic range optimization: Shown as range checked for each record in EXPLAIN output; each outer row causes a re-run of the range optimizer. Those features can be excluded from tracing by setting one or more switches of the ... Some ...
https://dev.mysql.com/doc/refman/5.7/en/optimizer-trace-system-variable.html
The optimizer_trace system variable has these on/off switches: enabled: Enables (ON) or disables (OFF) tracing one_line: If set to ON, the trace contains no whitespace, thus conserving space. This renders the trace difficult to read for humans, ...
https://dev.mysql.com/doc/refman/5.7/en/optimizer-tracing.html
The MySQL optimizer includes the capability to perform tracing; the interface is provided by a set of optimizer_trace_xxx system variables and the INFORMATION_SCHEMA.OPTIMIZER_TRACE table.
https://dev.mysql.com/doc/refman/5.7/en/optimizing-subqueries.html
Development is ongoing, so no optimization tip is reliable for the long term. For example: SELECT * FROM t1 WHERE t1.column1 IN (SELECT column1 FROM t2 ORDER BY column1); SELECT * FROM t1 WHERE t1.column1 IN (SELECT DISTINCT column1 FROM t2); ...
https://dev.mysql.com/doc/refman/5.7/en/out-of-memory.html
This causes it to use the mysql_use_result() C API function to retrieve the result set, which places less of a load on the client (but more on the server). Is it reasonable that it should return so many rows? If not, correct the query and try again.