Search Results
https://dev.mysql.com/doc/refman/8.4/en/show-relaylog-events.html
The LIMIT clause has the same syntax as for the SELECT statement. Note Issuing a SHOW RELAYLOG EVENTS with no LIMIT clause could start a very time- and resource-consuming process because the server returns to the client the complete contents of the ... SHOW RELAYLOG EVENTS [IN 'log_name'] [FROM pos] [LIMIT [offset,] row_count] [channel_option] channel_option: FOR CHANNEL channel Shows the events in the relay log of a ...
https://dev.mysql.com/doc/refman/8.4/en/purge-binary-logs.html
The PURGE BINARY LOGS statement deletes all the binary log files listed in the log index file prior to the specified log file name or date. (Bug #18199, Bug #18453) To handle such errors, edit the .index file (which is a simple text file) manually ...The log consists of a set of binary log files, plus an index file (see Section 7.4.4, “The Binary ... PURGE BINARY LOGS { TO 'log_name' | BEFORE datetime_expr } The ...
https://dev.mysql.com/doc/refman/8.4/en/extended-show.html
Some extensions to SHOW statements accompany the implementation of INFORMATION_SCHEMA: SHOW can be used to get information about the structure of INFORMATION_SCHEMA itself. Several SHOW statements accept a WHERE clause that provides more ...
https://dev.mysql.com/doc/refman/8.4/en/show.html
The pattern is useful for restricting statement output to matching values. Several SHOW statements also accept a WHERE clause that provides more flexibility in specifying which rows to display. In SHOW statement results, user names and host names ...
https://dev.mysql.com/doc/internals/en/prepared-stored-reexecution.html
Features of MySQL 4.1 and 5.0 put a new demand on the execution process: prepared statements and stored routines need to reuse the same parsed tree to execute a query many times. Later this memory root will be denoted as the permanent memory root ...So far no easy mechanism that would allow query reexecution using the conventional query processing code has been ...
https://dev.mysql.com/doc/heatwave/en/mys-hw-select.html
This topic provides information related to the SELECT statement clauses supported in MySQL HeatWave and describes how to use the GROUP BY and QUALIFY clauses to group or filter the processing results. SELECT STATEMENT Clauses The following SELECT ...Verify if the query is offloaded to MySQL HeatWave for ...
https://dev.mysql.com/doc/refman/8.4/en/deallocate-prepare.html
{DEALLOCATE | DROP} PREPARE stmt_name To deallocate a prepared statement produced with PREPARE, use a DEALLOCATE PREPARE statement that refers to the prepared statement name. Attempting to execute a prepared statement after deallocating it results ...
https://dev.mysql.com/doc/refman/8.4/en/declare-cursor.html
DECLARE cursor_name CURSOR FOR select_statement This statement declares a cursor and associates it with a SELECT statement that retrieves the rows to be traversed by the cursor. The number of columns retrieved by the SELECT statement must match the ...Cursor declarations must appear before handler declarations and after variable and condition ...
https://dev.mysql.com/doc/refman/8.4/en/drop-role.html
To use this statement, you must have the global DROP ROLE or CREATE USER privilege. Users who have the CREATE USER privilege can use this statement to drop accounts that are locked or unlocked. Users who have the DROP ROLE privilege can use this ...
https://dev.mysql.com/doc/refman/8.4/en/drop-user.html
The DROP USER statement removes one or more MySQL accounts and their privileges. (That is, the statement fails if dropping an account would cause a stored object to become orphaned.) To perform the operation anyway, you must have the SET_ANY_DEFINER ...It removes privilege rows for the account from all grant ...