PDF (US Ltr)
- 43.1Mb
PDF (A4)
- 43.2Mb
Man Pages (TGZ)
- 296.0Kb
Man Pages (Zip)
- 401.3Kb
Info (Gzip)
- 4.3Mb
Info (Zip)
- 4.3Mb
Search Results
https://dev.mysql.com/doc/refman/8.0/en/enterprise-encryption-configuring.html
MySQL Enterprise Encryption lets you limit keys to a length that provides adequate security for your requirements while balancing this with resource usage. You can also configure the functions provided by the component_enterprise_encryption ...
https://dev.mysql.com/doc/refman/8.0/en/explain-output.html
The EXPLAIN statement provides information about how MySQL executes statements. EXPLAIN returns a row of information for each table used in the SELECT statement. It lists the tables in the output in the order that MySQL would read them while ...
https://dev.mysql.com/doc/refman/8.0/en/gtid-functions.html
The functions described in this section are used with GTID-based replication. It is important to keep in mind that all of these functions take string representations of GTID sets as arguments. As such, the GTID sets must always be quoted when used ...
https://dev.mysql.com/doc/refman/8.0/en/information-schema-innodb-ft-config-table.html
The INNODB_FT_CONFIG table provides metadata about the FULLTEXT index and associated processing for an InnoDB table. Before querying it, set the value of the innodb_ft_aux_table system variable to the name (including the database name) of the table ...
https://dev.mysql.com/doc/refman/8.0/en/information-schema-innodb-ft-default-stopword-table.html
The INNODB_FT_DEFAULT_STOPWORD table holds a list of stopwords that are used by default when creating a FULLTEXT index on InnoDB tables. For information about the default InnoDB stopword list and how to define your own stopword lists, see Section ...
https://dev.mysql.com/doc/refman/8.0/en/information-schema-innodb-indexes-table.html
For related usage information and examples, see Section 17.15.3, “InnoDB INFORMATION_SCHEMA Schema Object Tables”. The INNODB_INDEXES table has these columns: INDEX_ID An identifier for the index. Index identifiers are unique across all the ...
https://dev.mysql.com/doc/refman/8.0/en/memory-storage-engine.html
The MEMORY storage engine (formerly known as HEAP) creates special-purpose tables with contents that are stored in memory. Because the data is vulnerable to crashes, hardware issues, or power outages, only use these tables as temporary work areas ...
https://dev.mysql.com/doc/refman/8.0/en/mysql-cluster-limitations-syntax.html
Some SQL statements relating to certain MySQL features produce errors when used with NDB tables, as described in the following list: Temporary tables. Trying either to create a temporary table that uses the NDB storage engine or to alter an ...
https://dev.mysql.com/doc/refman/8.0/en/mysql-cluster-ndbinfo-memoryusage.html
Querying this table provides information similar to that provided by the ALL REPORT MemoryUsage command in the ndb_mgm client, or logged by ALL DUMP 1000. The memoryusage table contains the following columns: node_id The node ID of this data node.
https://dev.mysql.com/doc/refman/8.0/en/mysql-cluster-ndbinfo.html
ndbinfo is a database containing information specific to NDB Cluster. This database contains a number of tables, each providing a different sort of data about NDB Cluster node status, resource usage, and operations. You can find more detailed ...