Server SQL Modes
534
The page size used for the memory-mapped implementation of the XA recovery log. The default
value is determined using
getpagesize()
. Currently, this variable is unused for the same reasons
as described for
Tc_log_max_pages_used
[533]
. Added in MySQL 5.0.3.
•
Tc_log_page_waits
[534]
For the memory-mapped implementation of the recovery log, this variable increments each time the
server was not able to commit a transaction and had to wait for a free page in the log. If this value is
large, you might want to increase the log size (with the
--log-tc-size
[413]
option). For binary
log-based recovery, this variable increments each time the binary log cannot be closed because
there are two-phase commits in progress. (The close operation waits until all such transactions are
finished.) Added in MySQL 5.0.3.
•
Threads_cached
[534]
The number of threads in the thread cache.
•
Threads_connected
[534]
The number of currently open connections.
•
Threads_created
[534]
The number of threads created to handle connections. If
Threads_created
[534]
is big, you may
want to increase the
thread_cache_size
[499]
value. The cache miss rate can be calculated as
Threads_created
[534]
/
Connections
[524]
.
•
Threads_running
[534]
The number of threads that are not sleeping.
•
Uptime
[534]
The number of seconds that the server has been up.
•
Uptime_since_flush_status
[534]
The number of seconds since the most recent
FLUSH STATUS
statement. This variable was added
in 5.0.35. (MySQL Community only)
5.1.7. Server SQL Modes
The MySQL server can operate in different SQL modes, and can apply these modes differently for
different clients. This capability enables each application to tailor the server's operating mode to its own
requirements.
For answers to some questions that are often asked about server SQL modes in MySQL, see
Section B.3, “MySQL 5.0 FAQ: Server SQL Mode”
.
Modes define what SQL syntax MySQL should support and what kind of data validation checks it
should perform. This makes it easier to use MySQL in different environments and to use MySQL
together with other database servers.
You can set the default SQL mode by starting
mysqld
with the
--sql-mode="modes"
[422]
option,
or by using
sql-mode="modes"
[422]
in
my.cnf
(Unix operating systems) or
my.ini
(Windows).
modes
is a list of different modes separated by comma (“
,
”) characters. The default value is empty (no
modes set). The
modes
value also can be empty (
--sql-mode=""
[422]
on the command line, or
sql-mode=""
[422]
in
my.cnf
on Unix systems or in
my.ini
on Windows) if you want to clear it
explicitly.
You can change the SQL mode at runtime by using a
SET [GLOBAL|SESSION]
sql_mode='modes'
statement to set the
sql_mode
[495]
system value. Setting the
GLOBAL
Summary of Contents for 5.0
Page 1: ...MySQL 5 0 Reference Manual ...
Page 18: ...xviii ...
Page 60: ...40 ...
Page 396: ...376 ...
Page 578: ...558 ...
Page 636: ...616 ...
Page 844: ...824 ...
Page 1234: ...1214 ...
Page 1427: ...MySQL Proxy Scripting 1407 ...
Page 1734: ...1714 ...
Page 1752: ...1732 ...
Page 1783: ...Configuring Connector ODBC 1763 ...
Page 1793: ...Connector ODBC Examples 1773 ...
Page 1839: ...Connector Net Installation 1819 2 You must choose the type of installation to perform ...
Page 2850: ...2830 ...
Page 2854: ...2834 ...
Page 2928: ...2908 ...
Page 3000: ...2980 ...
Page 3122: ...3102 ...
Page 3126: ...3106 ...
Page 3174: ...3154 ...
Page 3232: ...3212 ...