PDF (US Ltr)
- 43.3Mb
PDF (A4)
- 43.4Mb
Man Pages (TGZ)
- 297.2Kb
Man Pages (Zip)
- 402.4Kb
Info (Gzip)
- 4.3Mb
Info (Zip)
- 4.3Mb
Search Results
https://dev.mysql.com/doc/refman/8.0/en/myisamchk-general-options.html
The options described in this section can be used for any type of table maintenance operation performed by myisamchk. The sections following this one describe options that pertain only to specific operations, such as table checking or repairing.
https://dev.mysql.com/doc/refman/8.0/en/replication-rules-channel-based-filters.html
Channel specific replication filters are particularly useful in a multi-source replication topology when the same database or table is present on multiple sources, and the replica is only required to replicate it from one source. Overview of ...
https://dev.mysql.com/doc/refman/8.0/en/replication-privilege-checks.html
When REQUIRE_ROW_FORMAT is set for a replication channel, the replication applier does not create or drop temporary tables, and so does not set the pseudo_thread_id session system variable. The REQUIRE_TABLE_PRIMARY_KEY_CHECK option (available from ... By default, MySQL replication (including Group Replication) does not carry out privilege checks when transactions that were already accepted by another server are applied on a replica or group ...
https://dev.mysql.com/doc/refman/8.0/en/fulltext-search-ngram.html
Creating a FULLTEXT Index that Uses the ngram Parser To create a FULLTEXT index that uses the ngram parser, specify WITH PARSER ngram with CREATE TABLE, ALTER TABLE, or CREATE INDEX. The following example demonstrates creating a table with an ngram ...For a stopword list applicable to Chinese, Japanese, or Korean, you must create your ... The built-in MySQL full-text parser uses the white space between words as a delimiter to determine where words begin and end, ...
https://dev.mysql.com/doc/refman/8.0/en/column-indexes.html
For example: CREATE TABLE test (blob_col BLOB, INDEX(blob_col(10))); Prefixes can be up to 767 bytes long for InnoDB tables that use the REDUNDANT or COMPACT row format. Note Prefix limits are measured in bytes, whereas the prefix length in CREATE ...The maximum number of indexes per table and the maximum index length is defined per storage ... The most common type of index involves a single column, storing copies of the values from that ...
https://dev.mysql.com/doc/refman/8.0/en/ddl-rewriter.html
MySQL 8.0.16 and higher includes a ddl_rewriter plugin that modifies CREATE TABLE statements received by the server before it parses and executes them. The plugin removes ENCRYPTION, DATA DIRECTORY, and INDEX DIRECTORY clauses, which may be helpful ...Within statements considered for rewrite, instances of the following clauses are rewritten and each instance replaced by a single space: ENCRYPTION DATA DIRECTORY (at the table and partition levels) INDEX DIRECTORY (at the table and partition levels) Rewriting does not depend on ...
https://dev.mysql.com/doc/refman/8.0/en/view-algorithms.html
A reason to specify TEMPTABLE explicitly is that locks can be released on underlying tables after the temporary table has been created and before it is used to finish processing the statement. The optional ALGORITHM clause for CREATE VIEW or ALTER ...For MERGE, the text of a statement that refers to the view and the view definition are merged such that parts of the view definition replace corresponding parts of the ...
https://dev.mysql.com/doc/refman/8.0/en/mysqldump-delimited-text.html
The .sql file contains a CREATE TABLE statement for the table. The server sends the CREATE definitions for dumped tables to mysqldump, which writes them to .sql files. This section describes how to use mysqldump to create delimited-text dump files.
https://dev.mysql.com/doc/refman/8.0/en/features.html
Support for aliases on tables and columns as required by standard SQL. Support for MySQL-specific SHOW statements that retrieve information about databases, storage engines, tables, and indexes. You can refer to tables from different databases in ...
https://dev.mysql.com/doc/refman/8.0/en/innodb-limits.html
This section describes limits for InnoDB tables, indexes, tablespaces, and other aspects of the InnoDB storage engine. The index key prefix length limit is 3072 bytes for InnoDB tables that use DYNAMIC or COMPRESSED row format. The index key prefix ...For example, you might hit this limit with a column prefix index of more than 191 characters on a TEXT or VARCHAR column, assuming a utf8mb4 character set and the maximum of 4 bytes for each ...