#23833: drop all tables
-------------------------------------+-------------------------------------
Reporter: MattBlack85 | Owner: nobody
Type: New feature | Status: closed
Component: Core (Management | Version: master
commands) | Resolution: fixed
Severity: Normal | Triage Stage:
Keywords: | Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by yamila-moreno):
* status: new => closed
* needs_docs: => 0
* resolution: => fixed
* needs_tests: => 0
* needs_better_patch: => 0
Comment:
Talked to the author of the ticket. Add clarifying comment:
The main concern is that in the same database you may have tables
belonging and non-belonging the django project. In that scenario:
- dropdb : would cause losing all tables even those I would like to keep
- entering the db-shell and deleting tables one by one is boring and it's
easy to make a mistake
--
Ticket URL: <https://code.djangoproject.com/ticket/23833#comment:1>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
--
You received this message because you are subscribed to the Google Groups
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/069.2457c990188e9e2ff58d48d5fee3b637%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.