Debian Codegraph @

mysql-test/suite/storage_engine/strict_check_errors.inc

raw
1 #
2 # Since we run tests in disable_abort_on_error mode, we cannot use --error command,
3 # and need to check the result manually.
4 # Usage in a test:
5 # --let $error_codes = <comma-separated list> # optional, default ''
6 # --let $mysql_errname = <error name> # optional, default current $mysql_errname (from the last SQL command)
7 # --let $mysql_errno = <error code> # optional, default current $mysql_errno (from the last SQL command)
8 #
9 # The difference between strict_check_errors.inc and check_errors.inc is only
10 # that they will produce different messages when there is a list of acceptable error codes (more than one),
11 # and the statement finished with one of them.
12
13 # If a list contained more than one error, it could be on one of two reasons:
14 # first, we do not care which code it is, as long as it is one of the listed errors.
15 # In this case we will suggest to add an rdiff file if the message differs.
16 # Second, check_errors might be called from a generalized include file or test,
17 # which runs with different parameters and thus might produce different results for the same statement.
18 # Then, the message will be stricter, as the difference with the result file is actually a problem
19 # which needs to be checked at least.
20
21 --let $strict_check = 1
22 --source check_errors.inc
23