#24711: Flush manage command does not clear out migrations.
-------------------------------+--------------------------------------
Reporter: Pradeek | Owner: nobody
Type: Uncategorized | Status: new
Component: Migrations | Version: 1.8
Severity: Normal | Resolution:
Keywords: | Triage Stage: Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------+--------------------------------------
Changes (by timgraham):
* needs_better_patch: => 0
* needs_tests: => 0
* needs_docs: => 0
Comment:
Clearing the migrations history would mean that all schema migrations
would need to be faked. I think it would be easier to drop the database
and re-run the migrations. Attached is a proposed documentation patch to
suggest that. What do you think?
--
Ticket URL: <https://code.djangoproject.com/ticket/24711#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/065.875e5972fd2226aa4fd252403b2df1e1%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
