| Server IP : 88.99.149.37 / Your IP : 216.73.216.141 Web Server : nginx/1.31.2 System : Linux server-88-99-149-37 6.12.0-124.56.5.el10_1.x86_64 #1 SMP PREEMPT_DYNAMIC Fri May 15 06:12:08 EDT 2026 x86_64 User : muralimurth ( 1015) PHP Version : 8.4.23 Disable Function : exec,system,passthru,shell_exec,proc_close,proc_open,dl,popen,show_source,posix_kill,posix_mkfifo,posix_getpwuid,posix_setpgid,posix_setsid,posix_setuid,posix_setgid,posix_seteuid,posix_setegid,posix_uname MySQL : OFF | cURL : ON | WGET : ON | Perl : ON | Python : OFF | Sudo : ON | Pkexec : ON Directory : /usr/local/mysql/mysql-test/suite/storage_engine/ |
Upload File : |
# # 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