[SERVER-202] mongodump shouldn't dump the whole database directly Created: 30/Jul/09 Updated: 10/Sep/09 Resolved: 14/Aug/09 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Tools |
| Affects Version/s: | 0.9.7 |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Phillip Oldham | Assignee: | Eliot Horowitz (Inactive) |
| Resolution: | Won't Fix | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Participants: |
| Description |
|
Currently running mongodump without any arguments dumps all the databases. This could lead to accidental dumping, something which could be a problem if there is a large amount of data. Users coming from the MySQL world would expect mongodump to work in a similar way to mysqldump in that you must pass the argument `--all` or `-A` to dump all databases, and that calling the program without any arguments would show the help message. |
| Comments |
| Comment by Eliot Horowitz (Inactive) [ 10/Sep/09 ] |
|
closed b/c resolved more than 2 week ago |
| Comment by Eliot Horowitz (Inactive) [ 14/Aug/09 ] |
|
we've found in general that users like this behavior. |