File: strict_check_errors.inc

package info (click to toggle)
mariadb 1%3A11.8.3-1
  • links: PTS, VCS
  • area: main
  • in suites: sid
  • size: 772,520 kB
  • sloc: ansic: 2,414,714; cpp: 1,791,394; asm: 381,336; perl: 62,905; sh: 49,647; pascal: 40,897; java: 39,363; python: 20,791; yacc: 20,432; sql: 17,907; xml: 12,344; ruby: 8,544; cs: 6,542; makefile: 6,145; ada: 1,879; lex: 1,193; javascript: 996; objc: 80; tcl: 73; awk: 46; php: 22
file content (23 lines) | stat: -rw-r--r-- 1,300 bytes parent folder | download | duplicates (11)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
#
# Since we run tests in disable_abort_on_error mode, we cannot use --error command,
# and need to check the result manually.
# Usage in a test:
# --let $error_codes = <comma-separated list>  # optional, default ''
# --let $mysql_errname = <error name>          # optional, default current $mysql_errname (from the last SQL command)
# --let $mysql_errno = <error code>            # optional, default current $mysql_errno (from the last SQL command)
#
# The difference between strict_check_errors.inc and check_errors.inc is only 
# that they will produce different messages when there is a list of acceptable error codes (more than one),
# and the statement finished with one of them.

# If a list contained more than one error, it could be on one of two reasons:
# first, we do not care which code it is, as long as it is one of the listed errors.
# In this case we will suggest to add an rdiff file if the message differs.
# Second, check_errors might be called from a generalized include file or test, 
# which runs with different parameters and thus might produce different results for the same statement.
# Then, the message will be stricter, as the difference with the result file is actually a problem
# which needs to be checked at least.

--let $strict_check = 1
--source check_errors.inc