PDF (US Ltr)
- 35.1Mb
PDF (A4)
- 35.2Mb
Man Pages (TGZ)
- 256.4Kb
Man Pages (Zip)
- 361.3Kb
Info (Gzip)
- 3.4Mb
Info (Zip)
- 3.4Mb
Search Results
https://dev.mysql.com/doc/refman/5.7/en/privilege-changes.html
This may leave you wondering why your changes seem to make no difference! To tell the server to reload the grant tables, perform a flush-privileges operation. This can be done by issuing a FLUSH PRIVILEGES statement or by executing a mysqladmin ...
https://dev.mysql.com/doc/refman/5.7/en/problems-with-alias.html
This restriction is imposed because when the WHERE clause is evaluated, the column value may not yet have been determined. An alias can be used in a query select list to give a column a different name. In the select list of a query, a quoted column ...
https://dev.mysql.com/doc/refman/5.7/en/procedure-analyse.html
To obtain this analysis, append PROCEDURE ANALYSE to the end of a SELECT statement: SELECT ... This can be helpful for checking your existing tables, or after importing new data. This is used by ANALYSE() to check whether the optimal data type ...
https://dev.mysql.com/doc/refman/5.7/en/query-cache-operation.html
This section describes how the query cache works when it is operational. If this is not the case, the cached result is not used. This includes queries that use MERGE tables that map to the changed table. Note The query cache is deprecated as of ...
https://dev.mysql.com/doc/refman/5.7/en/query-cache-status-and-maintenance.html
Note The query cache is deprecated as of MySQL 5.7.20, and is removed in MySQL 8.0. To check whether the query cache is present in your MySQL server, use the following statement: mysql> SHOW VARIABLES LIKE 'have_query_cache'; ...
https://dev.mysql.com/doc/refman/5.7/en/recovery-from-backups.html
The full backup file is just a set of SQL statements, so restoring it is very easy: $> mysql < backup_sunday_1_PM.sql At this point, the data is restored to its state as of Sunday 1 p.m.. Now, suppose that we have a catastrophic unexpected exit on ...
https://dev.mysql.com/doc/refman/5.7/en/replica-connection-thread-states.html
Opening master dump table This state occurs after Creating table from master dump. Reading master dump table data This state occurs after Opening master dump table. Rebuilding the index on master dump table This state occurs after Reading master ...
https://dev.mysql.com/doc/refman/5.7/en/replication-administration-pausing.html
This makes it easier for the replica to catch up when you restart the replication SQL thread. This can be useful when you want to pause execution to catch up with events already received from the source, when you want to perform administration on ...
https://dev.mysql.com/doc/refman/5.7/en/replication-delayed.html
SQL_Remaining_Delay: When Slave_SQL_Running_State is Waiting until MASTER_DELAY seconds after master executed event, this field contains an integer indicating the number of seconds left of the delay. MySQL 5.7 supports delayed replication such that ...
https://dev.mysql.com/doc/refman/5.7/en/replication-features-auto-increment.html
(Bug #45677) An INSERT into a table that has a composite primary key that includes an AUTO_INCREMENT column that is not the first column of this composite key is not safe for statement-based logging or replication. (Bug #11754117, Bug #45670) This ... Statement-based replication of AUTO_INCREMENT, LAST_INSERT_ID(), and TIMESTAMP values is done correctly, subject to the following exceptions: When using statement-based replication prior to MySQL 5.7.1, AUTO_INCREMENT columns in tables on the replica must match the same columns on the source; that is, AUTO_INCREMENT columns must be replicated to AUTO_INCREMENT ...