PDF (US Ltr)
- 43.2Mb
PDF (A4)
- 43.3Mb
Man Pages (TGZ)
- 295.2Kb
Man Pages (Zip)
- 400.4Kb
Info (Gzip)
- 4.3Mb
Info (Zip)
- 4.3Mb
Search Results
https://dev.mysql.com/doc/refman/8.0/en/mysql-cluster-programs-ndb-select-count.html
ndb_select_count prints the number of rows in one or more NDB tables. You can obtain row counts from multiple tables in the same database by listing the table names separated by spaces when invoking this command, as shown under Sample Output. With ...
https://dev.mysql.com/doc/refman/8.0/en/deleting-from-related-tables.html
If the total length of the DELETE statement for related_table is more than the default value of the max_allowed_packet system variable, you should split it into smaller parts and execute multiple DELETE statements. You probably get the fastest ...
https://dev.mysql.com/doc/refman/8.0/en/fulltext-boolean.html
Whether a word is too short is determined from the innodb_ft_min_token_size setting for InnoDB tables, or ft_min_word_len for MyISAM tables. If the minimum word length is 4, a search for '+word +the*' could return fewer rows than a search for '+word ...| +----+-----------------------+-------------------------------------+ Note In implementing this feature, MySQL uses what is sometimes referred to as implied Boolean logic, in which + stands for AND - stands for NOT [no operator] implies OR Boolean full-text searches have these characteristics: They do not automatically sort rows in order of decreasing ...
https://dev.mysql.com/doc/refman/8.0/en/upgrading-from-previous-series.html
The error message is: mysql> ERROR 1709 (HY000): Index column size too large. The compressBound() function is called by InnoDB functions that determine the maximum row size permitted when creating compressed InnoDB tables or inserting and updating ...To determine the SRIDs contained in a geometry column col_name, use the following query: SELECT DISTINCT ST_SRID(col_name) FROM tbl_name; If the query returns more than one row, the column contains a mix of ...
https://dev.mysql.com/doc/refman/8.0/en/innodb-dedicated-server.html
Warning Automatic redo log capacity configuration behavior is undefined if innodb_buffer_pool_size is set to a value larger than the detected amount of server memory. When the server is started with --innodb-dedicated-server, InnoDB automatically ...You should consider using --innodb-dedicated-server only if the MySQL instance resides on a dedicated server where it can use all available system resources—for example, if you run MySQL Server in a Docker container or dedicated VM that runs MySQL ...
https://dev.mysql.com/doc/refman/8.0/en/index-statistics.html
When a given index value yields a large number of rows, the index is less useful and MySQL is less likely to use it. The SHOW INDEX statement displays a cardinality value based on N/S, where N is the number of rows in the table and S is the average ...Table statistics are based on value groups, where a value group is a set of rows with the same key prefix ...
https://dev.mysql.com/doc/refman/8.0/en/innodb-compression-usage.html
The actual compression algorithm is not affected by the KEY_BLOCK_SIZE value; the value determines how large each compressed chunk is, which in turn affects how many rows can be packed into each compressed page. After the innodb_file_per_table ...
https://dev.mysql.com/doc/refman/8.0/en/alter-user.html
ALTER USER permits these auth_option syntaxes: IDENTIFIED BY 'auth_string' [REPLACE 'current_auth_string'] [RETAIN CURRENT PASSWORD] Sets the account authentication plugin to the default plugin, passes the cleartext 'auth_string' value to the plugin ... ALTER USER [IF EXISTS] user [auth_option] [, user [auth_option]] ...
https://dev.mysql.com/doc/refman/8.0/en/bug-reports.html
If you cannot produce a test case with only a few rows, or if the test table is too big to be included in the bug report (more than 10 rows), you should dump your tables using mysqldump and create a README file that describes your problem. This ...
https://dev.mysql.com/doc/refman/8.0/en/innodb-compression-background.html
An InnoDB table created with ROW_FORMAT=COMPRESSED can use a smaller page size on disk than the configured innodb_page_size value. But if you specify a value that is too small, there is additional overhead to reorganize the pages when data values ...