mariadb Command-Line Client
mariadb is a simple SQL shell with GNU readline capabilities.
The command-line client is called mariadb. On Unix system, a symlink named mysql is available. On Windows, an alternative binary named mysql.exe is available.
Overview
mariadb supports interactive and non-interactive use. When used interactively, query results are presented in an ASCII-table format. When used non-interactively (for example, as a filter), the result is presented in tab-separated format. The output format can be changed using command options.
If you have problems due to insufficient memory for large result sets, use the--quick option. This forces mariadb to retrieve results from the server a row at a time rather than retrieving the entire result set and buffering it in memory before displaying it. This is done by returning the result set using the mysql_use_result() C API function in the client/server library rather than mysql_store_result().
Invoke the client from the prompt of your command interpreter (for instance, cmd on Windows, Terminal on macOS) as follows:
mariadb db_nameAlternatively, start the client and log on to MariaDB server:
mariadb --user=user_name --password=your_password db_nameType an SQL statement, end it with a semicolon (;), \g, or \G , and press Enter.
Typing Control-C causes mariadb to attempt to kill the current statement. If this cannot be done, or Control-C is typed again before the statement is killed, mariadb exits.
You can execute SQL statements in a script file (batch file) like this:
mariadb db_name < script.sql > output.tabUsage
The client's general syntax is:
mariadb <options>Options
mariadb supports the following options:
-?, --help
-?, --helpDisplay help and exit.
-I, --help
-I, --helpSynonym for -?
--abort-source-on-error
--abort-source-on-errorAbort 'source filename' operations in case of errors.
--auto-rehash
--auto-rehashEnable automatic rehashing. This option is on by default, which enables database, table, and column name completion. Use --disable-auto-rehash, --no-auto-rehash or skip-auto-rehash to disable rehashing. That causes mariadb to start faster, but you must issue the rehash command if you want to use name completion. To complete a name, enter the first part and press Tab. If the name is unambiguous, mariadb completes it. Otherwise, you can press Tab again to see the possible names that begin with what you have typed so far. Completion does not occur if there is no default database.
-A, --no-auto-rehash
-A, --no-auto-rehashNo automatic rehashing. One has to use 'rehash' to get table and field completion. This gives a quicker start of mariadb and disables rehashing on reconnect.
--auto-vertical-output
--auto-vertical-outputAutomatically switch to vertical output mode if the result is wider than the terminal width.
-B, --batch
-B, --batchPrint results using tab as the column separator, with each row on a new line. With this option, mariadb does not use the history file. Batch mode results in nontabular output format and escaping of special characters. Escaping may be disabled by using raw mode; see the description for the --raw option. (Enables --silent.)
--binary-mode
--binary-modeBy default, ASCII '\0' is disallowed and \r\n is translated to \n. This switch turns off both features, and also turns off parsing of all client commands except \C and DELIMITER, in non-interactive mode (for input piped to mariadb or loaded using the source command). This is necessary when processing output from mariadb-binlog that may contain blobs.
--character-sets-dir=name
--character-sets-dir=nameDirectory for character set files.
--column-names
--column-namesWrite column names in results. (Defaults to ON; use --skip-column-names to disable.)
--column-type-info
--column-type-infoDisplay column type information.
-c, --comments
-c, --commentsPreserve comments. Send comments to the server. The default is --skip-comments (discard comments), enable with --comments.
-C, --compress
-C, --compressCompress all information sent between the client and the server if both support compression.
--connect-expired-password
--connect-expired-passwordNotify the server that this client is prepared to handle expired password sandbox mode even if --batch was specified.
--connect-timeout=num
--connect-timeout=numNumber of seconds before connection timeout. Defaults to 0.
-D, --database=name
-D, --database=nameDatabase to use.
-``[options], --debug[=options]
-``[options], --debug[=options]On debugging builds, write a debugging log. A typical debug_options string is d:t:o,file_name. The default is d:t:o,/tmp/mysql.trace.
--debug-check
--debug-checkCheck memory and open file usage at exit.
-T, --debug-info
-T, --debug-infoPrint some debug info at exit.
--default-auth=plugin
--default-auth=pluginDefault authentication client-side plugin to use.
--default-character-set=name
--default-character-set=nameSet the default character set. A common issue that can occur when the operating system uses utf8 or another multibyte character set is that output from the mariadb client is formatted incorrectly, due to the fact that the MariaDB client uses the latin1 character set by default. You can usually fix such issues by using this option to force the client to use the system character set instead. If set to auto the character set is taken from the client environment (LC_CTYPE on Unix).
--defaults-extra-file=file
--defaults-extra-file=fileRead this file after the global files are read. Must be given as the first option.
--defaults-file=file
--defaults-file=fileOnly read default options from the given file. Must be given as the first option.
--defaults-group-suffix=suffix
--defaults-group-suffix=suffixIn addition to the given groups, also read groups with this suffix.
--delimiter=name
--delimiter=nameDelimiter to be used. The default is the semicolon (;).
--enable-cleartext-plugin
--enable-cleartext-pluginObsolete option. Exists only for MySQL compatibility.
-e, --execute=name
-e, --execute=nameExecute statement and quit. Disables --force and history file. The default output format is like that produced with --batch.
-f, --force
-f, --forceContinue even if we get an SQL error. Sets --abort-source-on-error to 0.
-h, --host=host
-h, --host=hostConnect to host.
-H, --html
-H, --htmlProduce HTML output.
-U, --i-am-a-dummy
-U, --i-am-a-dummySynonym for option --safe-updates, -U.
-i, --ignore-spaces
-i, --ignore-spacesIgnore space after function names. Allows one to have spaces (including tab characters and new line characters) between function name and '('. The drawback is that this causes built in functions to become reserved words.
--init-command=str
--init-command=strSQL Command to execute when connecting to the MariaDB server. Will automatically be re-executed when reconnecting.
--line-numbers
--line-numbersWrite line numbers for errors. (Defaults to ON; use --skip-line-numbers to disable.)
--local-infile
--local-infileEnable or disable LOCAL capability for LOAD DATA INFILE. With no value, the option enables LOCAL. The option may be given as--local-infile=0 or --local-infile=1 to explicitly disable or enable LOCAL. Enabling LOCAL has no effect if the server does not also support it.
--max-allowed-packet=num
--max-allowed-packet=numThe maximum packet length to send to or receive from server. The default is 16MB, the maximum 1GB.
--max-join-size=num
--max-join-size=numAutomatic limit for rows in a join when using --safe-updates. Default is 1000000.
-G, --named-commands
-G, --named-commandsEnable named commands. Named commands mean mariadb's internal commands (see below) . When enabled, the named commands can be used from any line of the query, otherwise only from the first line, before an enter. Long-format commands are allowed, not just short-format commands. For example, quit and \q are both recognized. Disable with --disable-named-commands. This option is disabled by default.
--net-buffer-length=num
--net-buffer-length=numThe buffer size for TCP/IP and socket communication. Default is 16KB.
-b, --no-beep
-b, --no-beepTurn off beep on error.
--no-defaults
--no-defaultsDon't read default options from any option file. Must be given as the first option.
-o, --one-database
-o, --one-databaseIgnore statements except those that occur while the default database is the one named on the command line. This filtering is limited, and based only on USE statements. This is useful for skipping updates to other databases in the binary log.
--pager[=name]
--pager[=name]Pager to use to display results (Unix only). If you don't supply an option, the default pager is taken from your ENV variable PAGER. Valid pagers are less, more, cat [> filename], etc. See interactive help (\h) also. This option does not work in batch mode. Disable with --disable-pager. This option is disabled by default.
-p, --password[=password]
-p, --password[=password]Password to use when connecting to server. If you use the short option form (-p), you cannot have a space between the option and the password. If you omit the password value following the --password or -p option on the command line, mariadb prompts for one. Specifying a password on the command line should be considered insecure. You can use an option file to avoid giving the password on the command line.
--plugin-dir=name
--plugin-dir=nameDirectory for client-side plugins.
-P, --port=num
-P, --port=numPort number to use for connection or 0 for default to, in order of preference, my.cnf, $MYSQL_TCP_PORT, /etc/services, built-in default (3306).
--print-defaults
--print-defaultsPrint the program argument list and exit. Must be given as the first option.
--progress-reports
--progress-reportsGet progress reports for long running commands (such as ALTER TABLE). (Defaults to ON; use --skip-progress-reports to disable.)
--prompt=name
--prompt=nameSet the mariadb prompt to this value. See prompt command for options.
--protocol=name
--protocol=nameThe protocol to use for connection (tcp, socket, pipe, memory).
-q, --quick
-q, --quickDon't cache result, print it row by row. This may slow down the server if the output is suspended. Doesn't use history file.
--quick-max-column-width=N
--quick-max-column-width=NMaximal field length limit in case of --quick.
-r, --raw
-r, --rawFor tabular output, the “boxing” around columns enables one column value to be distinguished from another. For nontabular output (such as is produced in batch mode or when the --batch or --silent option is given), special characters are escaped in the output so they can be identified easily. Newline, tab, NUL, and backslash are written as \n, \t, \0, and \\. The --raw option disables this character escaping.
--reconnect
--reconnectReconnect if the connection is lost. This option is enabled by default. Disable with --disable-reconnect or skip-reconnect.
-U, --safe-updates
-U, --safe-updatesAllow only those UPDATE and DELETE statements that specify which rows to modify by using key values. If you have set this option in an option file, you can override it by using --safe-updates on the command line. See using the --safe-updates option for more.
--sandbox
--sandboxDisallow commands that access the file system (except \P without an argument and \e). Disabled commands include system (\!), tee (\T), pager with an argument(\P foo), source (\.). Using a disabled command is an error, which can be ignored with --force. A sandbox command (\-) enables the sandbox mode until EOF (current file or the session, if interactive).
--script-dir
--script-dirSets an alternative directory path for searching scripts invoked via the source command.
--secure-auth
--secure-authRefuse client connecting to server if it uses old (pre-MySQL4.1.1) protocol. Defaults to FALSE.
--select-limit=num
--select-limit=numAutomatic limit for SELECT when using --safe-updates. Default 1000.
--server-arg=name
--server-arg=nameSend embedded server this as a parameter.
--shared-memory-base-name=name
--shared-memory-base-name=nameShared-memory name to use for Windows connections using shared memory to a local server (started with the --shared-memory option). Case-sensitive.
--show-serveroutput
--show-serveroutputEnables displaying of DBMS_OUTPUT messages. See this page for details.
--show-warnings
--show-warningsShow warnings after every statement. Applies to interactive and batch mode.
--sigint-ignore
--sigint-ignoreIgnore SIGINT signals (usually CTRL-C).
-s, --silent
-s, --silentBe more silent. This option can be given multiple times to produce less and less output. This option results in nontabular output format and escaping of special characters. Escaping may be disabled by using raw mode; see the description for the --raw option.
--skip-auto-rehash
--skip-auto-rehashDisable automatic rehashing. See --auto-rehash.
-N, --skip-column-names
-N, --skip-column-namesDon't write column names in results. See --column-names.
--skip-comments
--skip-commentsDiscard comments. Set by default, see --comments to enable.
-L, --skip-line-numbers
-L, --skip-line-numbersDon't write line number for errors. See --line-numbers.
--skip-progress-reports
--skip-progress-reportsDisables getting progress reports for long running commands. See --progress-reports.
--skip-reconnect
--skip-reconnectDon't reconnect if the connection is lost. See --reconnect.
-S, --socket=name
-S, --socket=nameFor connections to localhost, the Unix socket file to use, or, on Windows, the name of the named pipe to use. The socket file can exist in different locations depending on setup. Common locations include:
Debian-based, Ubuntu:
/var/run/mysqld/mysqld.sockSUSE:
/var/run/mysql/mysql.sockRed Hat:
/var/lib/mysql/mysql.sockOther:
/tmp/mysql.sock
--ssl
--sslEnables TLS. TLS is also enabled even without setting this option when certain other TLS options are set. The --ssl option does not enable verifying the server certificate by default. In order to verify the server certificate, the user must specify the --ssl-verify-server-cert option.
TLS with --ssl is enabled by default.
--ssl-ca=name
--ssl-ca=nameDefines a path to a PEM file that should contain one or more X509 certificates for trusted Certificate Authorities (CAs) to use for TLS. This option requires that you use the absolute path, not a relative path. See Secure Connections Overview: Certificate Authorities (CAs) for more information. This option implies the --ssl option.
--ssl-capath=name
--ssl-capath=nameDefines a path to a directory that contains one or more PEM files that should each contain one X509 certificate for a trusted Certificate Authority (CA) to use for TLS. This option requires that you use the absolute path, not a relative path. The directory specified by this option needs to be run through the openssl rehash command. See Secure Connections Overview: Certificate Authorities (CAs) for more information. This option is only supported if the client was built with OpenSSL or yaSSL. If the client was built with GnuTLS or Schannel, then this option is not supported. See TLS and Cryptography Libraries Used by MariaDB for more information about which libraries are used on which platforms. This option implies the --ssl option.
--ssl-cert=name
--ssl-cert=nameDefines a path to the X509 certificate file to use for TLS. This option requires that you use the absolute path, not a relative path. This option implies the --ssl option.
--ssl-cipher=name
--ssl-cipher=nameList of permitted ciphers or cipher suites to use for TLS. This option implies the --ssl option.
--ssl-crl=name
--ssl-crl=nameDefines a path to a PEM file that should contain one or more revoked X509 certificates to use for TLS. This option requires that you use the absolute path, not a relative path. See Secure Connections Overview: Certificate Revocation Lists (CRLs) for more information. This option is only supported if the client was built with OpenSSL or Schannel. If the client was built with yaSSL or GnuTLS, then this option is not supported. See TLS and Cryptography Libraries Used by MariaDB for more information about which libraries are used on which platforms.
--ssl-crlpath=name
--ssl-crlpath=nameDefines a path to a directory that contains one or more PEM files that should each contain one revoked X509 certificate to use for TLS. This option requires that you use the absolute path, not a relative path. The directory specified by this option needs to be run through the openssl rehash command. See Secure Connections Overview: Certificate Revocation Lists (CRLs) for more information. This option is only supported if the client was built with OpenSSL. If the client was built with yaSSL, GnuTLS, or Schannel, then this option is not supported. See TLS and Cryptography Libraries Used by MariaDB for more information about which libraries are used on which platforms.
--ssl-key=name
--ssl-key=nameDefines a path to a private key file to use for TLS. This option requires that you use the absolute path, not a relative path. This option implies the --ssl option.
--ssl-verify-server-cert
--ssl-verify-server-certEnables server certificate verification. This option is enabled by default. Use --disable-ssl or --disable-ssl-verify-server-cert to revert this behavior.
-t, --table
-t, --tableDisplay output in table format. This is the default for interactive use, but can be used to produce table output in batch mode.
--tee=name
--tee=nameAppend everything into outfile. See interactive help (\h) also. Does not work in batch mode. Disable with --disable-tee. This option is disabled by default.
--tls-version=name
--tls-version=nameThis option accepts a comma-separated list of TLS protocol versions. A TLS protocol version will only be enabled if it is present in this list. All other TLS protocol versions will not be permitted. See Secure Connections Overview: TLS Protocol Versions for more information.
--ssl-fp=name
--ssl-fp=nameServer certificate fingerprint (implies --ssl).
--ssl-fplist=name
--ssl-fplist=nameFile with accepted server certificate fingerprints, one per line (implies --ssl).
-n, --unbuffered
-n, --unbufferedFlush buffer after each query.
-u, --user=name
-u, --user=nameUser for login if not current user.
-v, --verbose
-v, --verboseWrite more. (-v -v -v gives the table output format).
-V, --version
-V, --versionOutput version information and exit.
-E, --vertical
-E, --verticalPrint the output of a query (rows) vertically. Use the \G delimiter to apply to a particular statement if this option is not enabled.
-w, --wait
-w, --waitIf the connection cannot be established, wait and retry instead of aborting.
-X, --xml
-X, --xmlProduce XML output. See the mariadb-dump --xml option for more.
Option Files
In addition to reading options from the command line, mariadb can also read options from option files. If an unknown option is provided to mariadb in an option file, then it is ignored.
The following options relate to how MariaDB command line tools handles option files. They must be given as the first argument on the command line:
--print-defaults
Print the program argument list and exit.
--no-defaults
Don't read default options from any option file.
--defaults-file=#
Only read default options from the given file #.
--defaults-extra-file=#
Read this file after the global files are read.
--defaults-group-suffix=#
In addition to the default option groups, also read option groups with this suffix. If not set, MariaDB checks the $MYSQL_GROUP_SUFFIX environment variable. From MariaDB 12.0.1, MariaDB 11.8.2, MariaDB 11.4.6, MariaDB 10.11.12, $MARIADB_GROUP_SUFFIX is also checked, and takes precedence if both are set.
mariadb is linked with MariaDB Connector/C. However, MariaDB Connector/C does not handle the parsing of option files for this client. That is performed by the server option file parsing code. See MDEV-19035 for more information.
Option Groups
mariadb reads options from the following option groups from option files:
[mysql]
Options read by mysql, which includes both MariaDB Server and MySQL Server.
[mariadb-client]
Options read by mariadb.
[client]
Options read by all MariaDB and MySQL client programs, which includes both MariaDB and MySQL clients. For example, mysqldump.
[client-server]
Options read by all MariaDB client programs and the MariaDB Server. This is useful for options like socket and port, which is common between the server and the clients.
[client-mariadb]
Options read by all MariaDB client programs.
Delimiters
The default delimiter in the mariadb client is the semicolon.
When creating stored programs from the command line, it is likely you will need to differentiate between the regular delimiter and a delimiter inside a BEGIN END block. Consider the following example:
CREATE FUNCTION FortyTwo() RETURNS TINYINT DETERMINISTIC
BEGIN
DECLARE x TINYINT;
SET x = 42;
RETURN x;
END;If you enter the above line by line, the mariadb client will treat the first semicolon, at the end of the DECLARE x TINYINT line, as the end of the statement. Since that's only a partial definition, it will throw a syntax error, as follows:
CREATE FUNCTION FortyTwo() RETURNS TINYINT DETERMINISTIC
BEGIN
DECLARE x TINYINT;
ERROR 1064 (42000): You have an error in your SQL syntax;
check the manual that corresponds to your MariaDB server version
for the right syntax to use near '' at line 3The solution is to specify a distinct delimiter for the duration of the process, using the DELIMITER. The delimiter can be any set of characters you choose, but it needs to be a distinctive set of characters that won't cause further confusion. // is a common choice, and used throughout the documentation.
Here's how the function can be entered, using the new delimiter:
DELIMITER //
CREATE FUNCTION FortyTwo() RETURNS TINYINT DETERMINISTIC
BEGIN
DECLARE x TINYINT;
SET x = 42;
RETURN x;
END
//
DELIMITER ;At the end, the delimiter is restored to the default semicolon. The \g and \G delimiters can always be used, even when a custom delimiter is specified.
Specify Which Protocol to Use
You can force which protocol are used to connect to the mariadbd server, by giving the protocol option one of the following values: tcp, socket, pipe , or memory.
A connection property specified via the command line (e.g. --port=3306) forces its type. The protocol that matches the respective connection property is used. For instance, a TCP/IP connection is created when --port is specified.
If multiple or no connection properties are specified via the command line, the following happens on Unix and Windows systems:
Unix
If
hostnameis not specified orhostnameislocalhost, Unix sockets are used.In other cases (
hostnameis given and it's notlocalhost) then a TCP/IP connection through theportoption is used.
localhost is a special value. Using 127.0.0.1 is not the same thing. The latter will connect to the mariadbd server through TCP/IP.
Windows
If
shared-memory-base-nameis specified andhostnameis not specified orhostnameislocalhost, then the connection will happen through shared memory.If
shared-memory-base-nameis not specified andhostnameis not specified orhostnameislocalhost, then the connection will happen through windows named pipes.Named pipes will also be used if the
libmysql/libmariadbclient library detects that the client doesn't support TCP/IP.In other cases, a TCP/IP connection through the
portoption is used.
Test Which Protocol is Used
The status command shows you information about which protocol is used:
shell> mariadb test
Welcome to the MariaDB monitor. Commands end with ; or \g.
Your MariaDB connection id is 3
Server version: 11.4.1-MariaDB MariaDB Server
Copyright (c) 2000, 2018, Oracle, MariaDB Corporation Ab and others.
Type 'help;' or '\h' for help. Type '\c' to clear the current input statement.
MariaDB [test]> status;
--------------
mysql Ver 15.1 Distrib 10.0.25-MariaDB, for Linux (x86_64) using readline 5.2
Connection id: 10
Current database: test
Current user: monty@localhost
...
Connection: Localhost via UNIX socket
...
UNIX socket: /tmp/mysql-dbug.sockmariadb Commands
There are also a number of commands that can be run inside the client. Note that all text commands must be first on the line and end with a semicolon (;).
-
Enables sandbox mode until EOF (current file or the session, if interactive). From MariaDB 10.5.25, MariaDB 10.6.18, MariaDB 10.11.8, MariaDB 11.0.6, MariaDB 11.1.5, MariaDB 11.2.4, MariaDB 11.4.2.
?, ?
Synonym for `help'.
clear, \c
Clear the current input statement.
connect,
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 mariadb server, display result vertically.
exit, \q
Exit mariadb. Same as quit.
go, \g
Send command to mariadb server.
help, \h
Display this help.
nopager,
Disable pager, print to stdout.
noserveroutput, \o
Disables displaying of DBMS_OUTPUT messages. See this page for details.
notee,
Don't write into outfile.
pager, \P
Set PAGER [to_pager]. Print the query results via PAGER.
print, \p
Print current command.
prompt,
Change your mariadb prompt.
quit, \q
Quit mariadb.
rehash, #
Rebuild completion hash.
serveroutput, \O
Enables displaying of DBMS_OUTPUT messages. See this page for details.
source, .
Execute an SQL script file. Takes a file name as an argument. Usually looks in the working directory, unless, from MariaDB 12.0, a path is given with --script-dir.
status, \s
Get status information from the server.
system, !
Execute a system shell command. Only works in Unix-like systems.
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.
nowarning, \w
Don't show warnings after every statement.
The mysql_history File
On Unix, the mariadb client writes a record of executed statements to a history file. By default, this file is named .mysql_history and is created in your home directory. To specify a different file, set the value of the MYSQL_HISTFILE environment variable.
The .mysql_history file should be protected with a restrictive access mode because sensitive information might be written to it, such as the text of SQL statements that contain passwords.
If you do not want to maintain a history file, first remove .mysql_history if it exists, and use either of the following techniques:
Set the
MYSQL_HISTFILEvariable to/dev/null. To cause this setting to take effect each time you log in, put the setting in one of your shell's startup files.Create
.mysql_historyas a symbolic link to/dev/null:
shell> ln -s /dev/null $HOME/.mysql_historyYou need do this only once.
prompt Command
The prompt command reconfigures the default prompt \N [\d]>. The string for defining the prompt can contain the following special sequences.
\c
A counter that increments for each statement you issue.
\D
The full current date.
\d
The default database.
\h
The server host.
\l
The current delimiter.
\m
Minutes of the current time.
\n
A newline character.
\O
The current month in three-letter format (Jan, Feb, ...).
\o
The current month in numeric format.
\P
am/pm.
\p
The current TCP/IP port or socket file.
\R
The current time, in 24-hour military time (0–23).
\r
The current time, standard 12-hour time (1–12).
\S
Semicolon.
\s
Seconds of the current time.
\t
A tab character.
\U
Your full user_name@host_name account name.
\u
Your user name.
\v
The server version.
\w
The current day of the week in three-letter format (Mon, Tue, ...).
\Y
The current year, four digits.
\y
The current year, two digits.
_
A space.
\
A space (a space follows the backslash).
'
Single quote.
"
Double quote.
\\
A literal “\” backslash character.
\x
x, for any “x” not listed above.
mariadb Tips
This section describes some techniques that can help you use mariadb more effectively.
Displaying Query Results Vertically
Some query results are much more readable when displayed vertically, instead of in the usual horizontal table format. Queries can be displayed vertically by terminating the query with \G instead of a semicolon (;). For example, longer text values that include newlines often are much easier to read with vertical output:
mariadb> SELECT * FROM mails WHERE LENGTH(txt) < 300 LIMIT 300,1\G
*************************** 1. row ***************************
msg_nro: 3068
date: 2000-03-01 23:29:50
time_zone: +0200
mail_from: Monty
reply: monty@no.spam.com
mail_to: "Thimble Smith" <tim@no.spam.com>
sbj: UTF-8
txt: >>>>> "Thimble" == Thimble Smith writes:
Thimble> Hi. I think this is a good idea. Is anyone familiar
Thimble> with UTF-8 or Unicode? Otherwise, I´ll put this on my
Thimble> TODO list and see what happens.
Yes, please do that.
Regards,
Monty
file: inbox-jani-1
hash: 190402944
1 row in set (0.09 sec)Using the --safe-updates Option
For beginners, a useful startup option is --safe-updates (or--i-am-a-dummy, which has the same effect). It is helpful for cases when you might have issued aDELETE FROM tbl_name statement but forgotten theWHERE clause. Normally, such a statement deletes all rows from the table. With --safe-updates, you can delete rows only by specifying the key values that identify them. This helps prevent accidents.
When you use the --safe-updates option, mariadb issues the following statement when it connects to the MariaDB server:
SET sql_safe_updates=1, sql_select_limit=1000, sql_max_join_size=1000000;The SET statement has the following effects:
UPDATE tbl_name SET not_key_column=val WHERE key_column=val;
UPDATE tbl_name SET not_key_column=val LIMIT 1;The server limits all large
SELECTresults to 1,000 rows unless the statement includes aLIMITclause.The server aborts multiple-table
SELECTstatements that probably need to examine more than 1,000,000 row combinations.
To specify limits different from 1,000 and 1,000,000, you can override the defaults by using the --select_limit and --max_join_size options:
mariadb --safe-updates --select_limit=500 --max_join_size=10000Disabling mariadb Auto-Reconnect
If the mariadb client loses its connection to the server while sending a statement, it immediately and automatically tries to reconnect once to the server and send the statement again. However, even if mariadb succeeds in reconnecting, your first connection has ended and all your previous session objects and settings are lost: temporary tables, the autocommit mode, and user-defined and session variables. Also, any current transaction rolls back. This behavior may be dangerous for you, as in the following example where the server was shut down and restarted between the first and second statements without you knowing it:
mariadb> SET @a=1;
Query OK, 0 rows affected (0.05 sec)
mariadb> INSERT INTO t VALUES(@a);
ERROR 2006: MySQL server has gone away
No connection. Trying to reconnect...
Connection id: 1
Current database: test
Query OK, 1 row affected (1.30 sec)
mariadb> SELECT * FROM t;
+------+
| a |
+------+
| NULL |
+------+The @a user variable has been lost with the connection, and after that, the reconnection it is undefined. If it is important to have mariadb terminate with an error if the connection has been lost, you can start the mariadb client with the --skip-reconnect option.
See Also
This page is licensed: CC BY-SA / Gnu FDL
Last updated
Was this helpful?

