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-config-file.html
When --initial is used, the global configuration file is re-read, any existing cache files are deleted, and the management server creates a new configuration cache. Note It is possible to roll back to a previous configuration by deleting later ...
https://dev.mysql.com/doc/refman/5.7/en/mysql-cluster-install-linux-binary.html
This section covers the steps necessary to install the correct executables for each type of Cluster node from precompiled binaries supplied by Oracle. For setting up a cluster using precompiled binaries, the first step in the installation process ...
https://dev.mysql.com/doc/refman/5.7/en/mysql-cluster-limitations-syntax.html
This is because an update of a primary key is implemented as a delete of the old row (containing the old primary key) plus an insert of the new row (with a new primary key). As of NDB 7.5.14 and NDB 7.6.10: ON DELETE CASCADE is not supported where ... Some SQL statements relating to certain MySQL features produce errors when used with NDB tables, as described in the following list: Temporary ...
https://dev.mysql.com/doc/refman/5.7/en/mysql-cluster-ndbinfo-memory-per-fragment.html
A fragment can have any number of fixed-size pages; when the last row on a fixed-size page is deleted, the page is released to the DataMemory page pool. Each variable-sized page is reorganized as needed to fit the changing size of variable-sized row ... memory_per_fragment Table: Notes memory_per_fragment Table: Examples The memory_per_fragment table provides information about the usage of memory by individual ...
https://dev.mysql.com/doc/refman/5.7/en/mysql-cluster-programs-ndb-restore.html
These tables are not needed afterwards, and are normally deleted by ndb_restore following a successful restoration. The NDB Cluster restoration program is implemented as a separate command-line utility ndb_restore, which can normally be found in ...
https://dev.mysql.com/doc/refman/5.7/en/mysql-logging.html
The mysql client can do these types of logging for statements executed interactively: On Unix, mysql writes the statements to a history file. By default, this file is named .mysql_history in your home directory. To specify a different file, set the ...
https://dev.mysql.com/doc/refman/5.7/en/mysql-nutshell.html
This includes SELECT, UPDATE, DELETE, CREATE TABLE, and other SQL statements. Previously, a table could have at most one trigger for each combination of trigger event (INSERT, UPDATE, DELETE) and action time (BEFORE, AFTER). This section summarizes ...
https://dev.mysql.com/doc/refman/5.7/en/mysqlbinlog.html
Warning The temporary files created for LOAD DATA LOCAL statements are not automatically deleted because they are needed until you actually execute those statements. You should delete the temporary files yourself after you no longer need the ... The ...
https://dev.mysql.com/doc/refman/5.7/en/optimizer-hints.html
The parser recognizes optimizer hint comments after the initial keyword of SELECT, UPDATE, INSERT, REPLACE, and DELETE statements. One means of control over optimizer strategies is to set the optimizer_switch system variable (see Section 8.9.2, ...
https://dev.mysql.com/doc/refman/5.7/en/optimizing-innodb-ddl-operations.html
Use TRUNCATE TABLE to empty a table, not DELETE FROM tbl_name. Foreign key constraints can make a TRUNCATE statement work like a regular DELETE statement, in which case a sequence of commands like DROP TABLE and CREATE TABLE might be fastest. Many ...