PDF (US Ltr)
- 43.3Mb
PDF (A4)
- 43.4Mb
Man Pages (TGZ)
- 297.2Kb
Man Pages (Zip)
- 402.5Kb
Info (Gzip)
- 4.3Mb
Info (Zip)
- 4.3Mb
Search Results
https://dev.mysql.com/doc/refman/8.0/en/pluggable-authentication.html
When a client connects to the MySQL server, the server uses the user name provided by the client and the client host to select the appropriate account row from the mysql.user system table. The server then authenticates the client, determining from ...Otherwise, the server invokes that plugin to authenticate the user, and the plugin returns a status to the server indicating whether the user provided the correct password and is permitted to ...
https://dev.mysql.com/doc/refman/8.0/en/problems-with-alias.html
An alias can be used in a query select list to give a column a different name. This restriction is imposed because when the WHERE clause is evaluated, the column value may not yet have been determined. In the select list of a query, a quoted column ...
https://dev.mysql.com/doc/refman/8.0/en/proxy-users.html
For example: GRANT PROXY ON 'proxied_user' TO 'proxy_user'; The statement creates a row in the mysql.proxies_priv grant table. The plugin that authenticates a given connection may request that the connecting (external) user be treated as a different ...
https://dev.mysql.com/doc/refman/8.0/en/replica-logs-status.html
Important Do not attempt to update or insert rows in the mysql.slave_master_info or mysql.slave_relay_log_info tables manually. A replica server creates two replication metadata repositories, the connection metadata repository and the applier ...
https://dev.mysql.com/doc/refman/8.0/en/replication-features-create-select.html
ROW format: The statement is logged as a CREATE TABLE statement followed by a series of insert-row events. SELECT always performs an implicit commit (Section 15.3.3, “Statements That Cause an Implicit Commit”). If the destination table does not ...
https://dev.mysql.com/doc/refman/8.0/en/replication-features-limit.html
SELECT statements is unsafe since the order of the rows affected is not defined. (Bug #42851) When using MIXED mode, the statement is now automatically replicated using row-based mode. Statement-based replication of LIMIT clauses in DELETE, UPDATE, ...
https://dev.mysql.com/doc/refman/8.0/en/replication-features-truncate.html
TRUNCATE TABLE is normally regarded as a DML statement, and so would be expected to be logged and replicated using row-based format when the binary logging mode is ROW or MIXED. However this caused issues when logging or replicating, in STATEMENT ...
https://dev.mysql.com/doc/refman/8.0/en/replication-features-variables.html
sql_mode is also replicated except for the NO_DIR_IN_CREATE mode; the replica always preserves its own value for NO_DIR_IN_CREATE, regardless of changes to it on the source. However, when mysqlbinlog parses a SET @@sql_mode = mode statement, the ...
https://dev.mysql.com/doc/refman/8.0/en/replication-features-views.html
Replication from a table to a same-named view is supported using statement-based logging, but not when using row-based logging. Trying to do so when row-based logging is in effect causes an error. Views are filtered by their own name, not by the ...
https://dev.mysql.com/doc/refman/8.0/en/replication-gtids.html
You can use either statement-based or row-based replication with GTIDs (see Section 19.2.1, “Replication Formats”); however, for best results, we recommend that you use the row-based format. This section explains transaction-based replication ...