diff options
| author | unknown <mleich@mysql.com> | 2005-01-26 10:19:28 +0100 |
|---|---|---|
| committer | unknown <mleich@mysql.com> | 2005-01-26 10:19:28 +0100 |
| commit | d42fbb43fd19946b1efe4b8ae960716730828494 (patch) | |
| tree | 5c1c68dc467aac46579749e23fd3618b57cb107b /mysql-test/r/testdb_only.require | |
| parent | 56bf2ce986d6a41e0b8359d3f60d77d949a0e597 (diff) | |
| download | mariadb-git-d42fbb43fd19946b1efe4b8ae960716730828494.tar.gz | |
WL#1420 convert NIST test for mysql
Test cases using common object (database,user,table,..) names could probably
destroy customer data, when connecting to an already running server.
This Changeset contains an auxiliary routine include/testdb_only.inc" which
should be sourced by tests doing such dangerous things.
The test case will get a "[skipped]" when the environment variable
USE_RUNNING_SERVER is not 0 .
The modified mysql-test-run.sh sets USE_RUNNING_SERVER to 0, when
the "mysql-test-run" starts its own server, aka there was no "--extern"
option.
mysql-test/mysql-test-run.sh:
If mysql-test-run spawns the server by itself, USE_RUNNING_SERVER will be set to 0 instead of "".
If the option "--extern" was detected, USE_RUNNING_SERVER will be set to 1 instead of "1".
Several comparisons have to be changed
[ -z "$USE_RUNNING_SERVER" ] --> [ $USE_RUNNING_SERVER -eq 0 ]
[ -n "$USE_RUNNING_SERVER" ] --> [ $USE_RUNNING_SERVER -eq 1 ]
USE_RUNNING_SERVER will be exported.
Diffstat (limited to 'mysql-test/r/testdb_only.require')
| -rw-r--r-- | mysql-test/r/testdb_only.require | 2 |
1 files changed, 2 insertions, 0 deletions
diff --git a/mysql-test/r/testdb_only.require b/mysql-test/r/testdb_only.require new file mode 100644 index 00000000000..e717418fdb6 --- /dev/null +++ b/mysql-test/r/testdb_only.require @@ -0,0 +1,2 @@ +Variable_name Value +use extern server NO |