Debian Codegraph @

mysql-test/suite/storage_engine/show_engine.test

raw
1 #
2 # SHOW ENGINE STATUS command
3 #
4 # The result might be empty, in which case the test will require rdiff,
5 # as it is optimistically expects some output from the command
6 #
7
8 --source have_engine.inc
9
10 --echo # For most engines SHOW ENGINE .. STATUS produces an empty result,
11 --echo # so the default result file is empty; but returning a value here is not an error.
12 --echo # The Status column is masked, because it is likely to contain some
13 --echo # volatile data (timestamps, memory info, etc.)
14
15 --source mask_engine.inc
16 --replace_column 3 '### Engine status, can be long and changeable ###'
17 eval
18 SHOW ENGINE $storage_engine STATUS;
19
20 --echo # For SHOW MUTEX even the number of lines is volatile, so the result logging is disabled,
21 --echo # the test only checks that the command does not produce any errors
22 --disable_result_log
23 --source mask_engine.inc
24 eval
25 SHOW ENGINE $storage_engine MUTEX;
26 --source mask_engine.inc
27 SHOW ENGINE ALL MUTEX;
28 --enable_result_log
29
30 --source cleanup_engine.inc
31