properly document env var for NO_DATABASE_NAME

Signed-off-by: Avi Deitcher <[email protected]>

Author: deitch

docs/backup.md

@@ -62,7 +62,7 @@ it will switch to the correct database when you restore the dump.
 If you do not want the `USE` statement in the backup file, for example if you might want to restore the dump to a different
 database, you need to remove the `USE <database>;` statement from the dump. `mysql-backup` does this for you when you set:
 
-* Environment variable: `NO_DATABASE_NAME=true`.
+* Environment variable: `DB_DUMP_NO_DATABASE_NAME=true`.
 * CLI flag: `--no-database-name=true`
 * Config file:
 ```yaml

docs/configuration.md

@@ -71,7 +71,7 @@ The following are the environment variables, CLI flags and configuration file op
 | path to file containing password for the database. `pass` takes precedence if both are set. | BR | `pass-file` | `DB_PASS_FILE` |  |  |
 | names of databases to dump, comma-separated | B | `include` | `DB_DUMP_INCLUDE` | `dump.include` | all databases in the server |
 | names of databases to exclude from the dump | B | `exclude` | `DB_DUMP_EXCLUDE` | `dump.exclude` |  |
-| do not include `USE <database>;` statement in the dump | B | `no-database-name` | `NO_DATABASE_NAME` | `dump.noDatabaseName` | `false` |
+| do not include `USE <database>;` statement in the dump | B | `no-database-name` | `DB_DUMP_NO_DATABASE_NAME` | `dump.noDatabaseName` | `false` |
 | Replace single long INSERT statement per table with one INSERT statement per line | B | `skip-extended-insert` | `DB_DUMP_SKIP_EXTENDED_INSERT` | `dump.skipExtendedInsert` | `false` |
 | restore to a specific database | R | `restore --database` | `RESTORE_DATABASE` | `restore.database` |  |
 | how often to do a dump or prune, in minutes | BP | `dump --frequency` | `DB_DUMP_FREQUENCY` | `dump.schedule.frequency` | `1440` (in minutes), i.e. once per day |