MySQL 9.1.0
Source Code Documentation
|
It is possible to run test cases against a production server.
This is very unlikely to happen by accident, as mysql-test-run.pl will start its own server unless you use the --extern
Even so, try to write test cases in a way that reduces the risk that running tests will alter or destroy important tables, views, or other objects. (DROP DATABASE statements are particularly dangerous if written using names that could exist on a customer's machine.) To avoid such problems, we recommend the following naming conventions:
User names: User names should begin with “mysql” (for example, mysqluser1, mysqluser2)
Database names: Unless you have a special reason not to, use the default database named test that is already created for you. For tests that need to operate outside the test database, database names should contain “test” or begin with “mysql” (for example, mysqltest1, mysqltest2)
Table names: t1, t2, t3, ...
For examples of how to name objects, examine the existing test cases. Of course, you can name columns and other objects inside tables as you wish.