#6011 closed Bug (fixed)
manage.py flush command not working as advertised
| Reported by: | Owned by: | nobody | |
|---|---|---|---|
| Component: | Core (Management commands) | Version: | dev |
| Severity: | Normal | Keywords: | |
| Cc: | Triage Stage: | Ready for checkin | |
| Has patch: | yes | Needs documentation: | no |
| Needs tests: | no | Patch needs improvement: | no |
| Easy pickings: | no | UI/UX: | no |
Description
If you run manage.py help flush, it indicates that it will be the same as if you ran the sql in manage.py sqlflush
However, once you try to run it, it starts prompting as if it's running syncdb, like reset does.
Flush should be a simple flush as advertised, while reset does the resetting.
Attachments (2)
Change History (8)
comment:1 by , 17 years ago
| Triage Stage: | Unreviewed → Accepted |
|---|
by , 17 years ago
| Attachment: | management-flush-helptext.diff added |
|---|
Updated help text for flush command
comment:3 by , 14 years ago
| Severity: | → Normal |
|---|---|
| Type: | → Bug |
by , 14 years ago
| Attachment: | 6011.flush-help.diff added |
|---|
comment:4 by , 14 years ago
| Easy pickings: | unset |
|---|
Simply replaced the help text with the one that's in the doc.
comment:5 by , 13 years ago
| Triage Stage: | Accepted → Ready for checkin |
|---|---|
| UI/UX: | unset |
Assuming Julien was not core-dev when this patch was attached.
Note:
See TracTickets
for help on using tickets.
Flush is intended to return the database to a post-sync state. It is used extensively by the testing system for this reason. In this case, the documentation is at fault and the behaviour is correct.
Reset operates on a per-app basis. As a result, cross-app references really mess with the reset command. I have mentioned a few times that I think
resetshould be deprecated, but we probably won't do so until such time as a schema evolution approach is introduced to trunk.