Oracle 5.0 Reference Manual page 556

•
ERROR_FOR_DIVISION_BY_ZERO
Produce an error in strict mode (otherwise a warning) when a division by zero (or
occurs during an
INSERT
for divisions by zero. For
divisions by zero, but the result of the operation is NULL. (Implemented in MySQL 5.0.2)
•
HIGH_NOT_PRECEDENCE
From MySQL 5.0.2 on, the precedence of the
NOT a BETWEEN b AND c
expression is parsed as
obtained by enabling the
mysql> SET sql_mode = '';
mysql> SELECT NOT 1 BETWEEN -5 AND 5;
-> 0
mysql> SET sql_mode = 'HIGH_NOT_PRECEDENCE';
mysql> SELECT NOT 1 BETWEEN -5 AND 5;
-> 1
• [536]
IGNORE_SPACE
Permit spaces between a function name and the "(" character. This causes built-in function names
to be treated as reserved words. As a result, identifiers that are the same as function names must
be quoted as described in
[970] function, the use of
COUNT()
error:
mysql> CREATE TABLE count (i INT);
ERROR 1064 (42000): You have an error in your SQL syntax
The table name should be quoted:
mysql> CREATE TABLE `count` (i INT);
Query OK, 0 rows affected (0.00 sec)
The
IGNORE_SPACE
or stored functions. It is always permissible to have spaces after a UDF or stored function name,
regardless of whether
For further discussion of
Resolution".
•
NO_AUTO_CREATE_USER
Prevent the statement from automatically creating new users if it would otherwise do so,
GRANT
unless a nonempty password also is specified. (Added in MySQL 5.0.2)
•
NO_AUTO_VALUE_ON_ZERO
NO_AUTO_VALUE_ON_ZERO
you generate the next sequence number for the column by inserting either
NO_AUTO_VALUE_ON_ZERO
next sequence number.
This mode can be useful if
is not a recommended practice, by the way.) For example, if you dump the table with
0
and then reload it, MySQL normally generates new sequence numbers when
mysqldump
it encounters the values, resulting in a table with contents different from the one that was
0
dumped. Enabling
NO_AUTO_VALUE_ON_ZERO
this problem.
mysqldump
NO_AUTO_VALUE_ON_ZERO
Server SQL Modes
[536]
or UPDATE. If this mode is not enabled, MySQL instead returns
or
INSERT IGNORE
[536]
are parsed as
NOT (a BETWEEN b AND
(NOT a) BETWEEN b AND
HIGH_NOT_PRECEDENCE
Section 9.2, "Schema Object
as a table name in the following statement causes an
count
[536] SQL mode applies to built-in functions, not to user-defined functions
[536]
IGNORE_SPACE
[536], see
IGNORE_SPACE
[536]
[536]
[536] affects handling of
[536] suppresses this behavior for
has been stored in a table's
0
now automatically includes in its output a statement that enables
[536], to avoid this problem.
536
IGNORE, MySQL generates a warning for
UPDATE
[880] operator is such that expressions such as
NOT
c. The old higher-precedence behavior can be
[536] SQL mode. (Added in MySQL 5.0.2)
Names". For example, because there is a
is enabled.
Section 9.2.3, "Function Name Parsing and
AUTO_INCREMENT
so that only
0
AUTO_INCREMENT
[536] before reloading the dump file solves
[911])
MOD(X,0)
NULL
c). Before MySQL 5.0.2, the
columns. Normally,
or into it.
NULL 0
generates the
NULL
column. (Storing