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/fulltext-natural-language.html
By default or with the IN NATURAL LANGUAGE MODE modifier, the MATCH() function performs a natural language search for a string against a text collection. A collection is a set of one or more columns included in a FULLTEXT index. For each row in the ...
https://dev.mysql.com/doc/refman/5.7/en/grant.html
[REQUIRE {NONE | tls_option [[AND] tls_option] ...}] [WITH {GRANT OPTION | resource_option} ...] GRANT PROXY ON user TO user [, user] ... To grant a privilege with GRANT, you must have the GRANT OPTION privilege, and you must have the privileges ...
https://dev.mysql.com/doc/refman/5.7/en/group-replication-limitations.html
Note that the limitations and issues described for multi-primary mode groups can also apply in single-primary mode clusters during a failover event, while the newly elected primary flushes out its applier queue from the old primary. Tip Group ...
https://dev.mysql.com/doc/refman/5.7/en/group-replication-network-partitioning.html
The group needs to achieve consensus whenever a change that needs to be replicated happens. This is the case for regular transactions but is also required for group membership changes and some internal messaging that keeps the group consistent.
https://dev.mysql.com/doc/refman/5.7/en/innodb-and-mysql-replication.html
It is possible to use replication in a way where the storage engine on the replica is not the same as the storage engine on the source. For example, you can replicate modifications to an InnoDB table on the source to a MyISAM table on the replica.
https://dev.mysql.com/doc/refman/5.7/en/innodb-autocommit-commit-rollback.html
If autocommit mode is enabled, each SQL statement forms a single transaction on its own. By default, MySQL starts the session for each new connection with autocommit enabled, so MySQL does a commit after each SQL statement if that statement did not ...
https://dev.mysql.com/doc/refman/5.7/en/innodb-compression-internals.html
This section describes some internal implementation details about compression for InnoDB tables. The information presented here may be helpful in tuning for performance, but is not necessary to know for basic use of compression. Compression ...
https://dev.mysql.com/doc/refman/5.7/en/innodb-next-key-locking.html
The so-called phantom problem occurs within a transaction when the same query produces different sets of rows at different times. For example, if a SELECT is executed twice, but returns a row the second time that was not returned the first time, ...
https://dev.mysql.com/doc/refman/5.7/en/innodb-online-ddl-operations.html
Online support details, syntax examples, and usage notes for DDL operations are provided under the following topics in this section. Index Operations Primary Key Operations Column Operations Generated Column Operations Foreign Key Operations Table ...
https://dev.mysql.com/doc/refman/5.7/en/innodb-online-ddl-single-multi.html
Before the introduction of online DDL, it was common practice to combine many DDL operations into a single ALTER TABLE statement. Because each ALTER TABLE statement involved copying and rebuilding the table, it was more efficient to make several ...