MySQL Client Commands

MySQLMySQLi Database

Let us understand some of the MySQL client commands −

MySQL sends every SQL statement that the user issues to the server so that it can be executed. There is also a set of commands that mysql interprets on its own.

Get the List of Commands

The list of these commands can be found by typing the below mentioned command on the prompt −

mysql> help

Output

List of all MySQL commands:
Note that all text commands must be first on line and end with ';'
? (\?) Synonym for `help'.
clear     (\c) Clear the current input statement.
connect   (\r) Reconnect to the server. Optional arguments are db and host.
delimiter (\d) Set statement delimiter.
edit      (\e) Edit command with $EDITOR.
ego       (\G) Send command to mysql server, display result vertically.
exit      (\q) Exit mysql. Same as quit.
go        (\g) Send command to mysql server.
help      (\h) Display this help.
nopager   (\n) Disable pager, print to stdout.
notee     (\t) Don't write into outfile.
pager     (\P) Set PAGER [to_pager]. Print the query results via PAGER.
print     (\p) Print current command.
prompt    (\R) Change your mysql prompt.
quit      (\q) Quit mysql.
rehash    (\#) Rebuild completion hash.
source    (\.) Execute an SQL script file. Takes a file name as an argument.
status    (\s) Get status information from the server.
system    (\!) Execute a system shell command.
tee       (\T) Set outfile [to_outfile]. Append everything into given    outfile.
use       (\u) Use another database. Takes database name as argument.
charset   (\C) Switch to another charset. Might be needed for processing  binlog with multi-byte charsets.
warnings  (\W) Show warnings after every statement.

If mysql is invoked with the ‘--binary-mode’ option, all mysql commands will be disabled except charset and delimiter in the non-interactive mode, given that the input is piped to mysql or loaded using the source command.

Each command has both a long and short form.

Long form commands

The long form is not case-sensitive whereas the short form is case-sensitive. The long form can be followed by an optional semicolon terminator, but the short form shouldn’t be followed by anything.

Short form commands

The use of short-form commands within multiple-line /* ... */ comments is not supported. Shortform commands work within single-line /*! ... */ version comments, so do /*+ ... */ optimizer-hint comments. They are stored in object definitions.

raja
Published on 10-Mar-2021 17:18:22
Advertisements