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/alter-user.html
Order of REQUIRE options does not matter, but no option can be specified twice. ALTER USER 'jeffrey'@'localhost' REQUIRE SUBJECT '/C=SE/ST=Stockholm/L=Stockholm/ O=MySQL demo client certificate/ CN=client/emailAddress=client@example.com'; MySQL does ... ALTER USER [IF EXISTS] user [auth_option] [, user [auth_option]] ...
https://dev.mysql.com/doc/refman/8.0/en/bnl-bka-optimization.html
The rows are fetched by the MRR functions in an optimal way: They are fetched in the row ID (primary key) order. This improves performance because reads are in disk order rather than random order. In MySQL, a Batched Key Access (BKA) Join algorithm ...
https://dev.mysql.com/doc/refman/8.0/en/character-arrays.html
<collation> elements indicate character ordering for comparison and sorting, one element per collation. Binary collations need no <map> element because the character codes themselves provide the ordering. For example: lower['A'] should contain 'a' ... Each simple character set has a configuration file located in the sql/share/charsets ...
https://dev.mysql.com/doc/refman/8.0/en/charset-collate.html
With the COLLATE clause, you can override whatever the default collation is for a comparison.
https://dev.mysql.com/doc/refman/8.0/en/charset-unicode.html
The MySQL implementation of UCS-2, UTF-16, and UTF-32 stores characters in big-endian byte order and does not use a byte order mark (BOM) at the beginning of values. Other database systems might use little-endian byte order or a BOM. The Unicode ...
https://dev.mysql.com/doc/refman/8.0/en/column-indexes.html
FULLTEXT queries that sort the matching rows in descending order of score and apply a LIMIT clause to take the top N matching rows. For this optimization to apply, there must be no WHERE clauses and only a single ORDER BY clause in descending order.
https://dev.mysql.com/doc/refman/8.0/en/condition-filtering.html
In general, the optimizer attempts to put tables with low prefix counts early in the join order to keep the number of row combinations from increasing rapidly. Ways to accomplish this include join-order optimizer hints (see Section 10.9.3, ... In ...
https://dev.mysql.com/doc/refman/8.0/en/converting-tables-to-innodb.html
When two transactions start modifying multiple tables, accessing the tables in a different order, they can reach a state where each transaction is waiting for the other and neither can proceed. If deadlock warnings occur constantly, you might review ... If you have MyISAM tables that you want to convert to InnoDB for better reliability and scalability, review the following guidelines and tips before ...
https://dev.mysql.com/doc/refman/8.0/en/create-user.html
Order of REQUIRE options does not matter, but no option can be specified twice. CREATE USER 'jeffrey'@'localhost' REQUIRE SUBJECT '/C=SE/ST=Stockholm/L=Stockholm/ O=MySQL demo client certificate/ CN=client/emailAddress=client@example.com'; MySQL ...
https://dev.mysql.com/doc/refman/8.0/en/data-dictionary-usage-differences.html
Consequently, depending on optimizer choices, the row order of results for INFORMATION_SCHEMA queries might differ from previous results. If a query result must have specific row ordering characteristics, include an ORDER BY clause. Use of a data ...