#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
-------------------------------+--------------------------------------
Comment (by Pradeek):
The reason why I proposed this, is because Django previously loaded
initial data during flush. Such a functionality cannot be replicated here
without going outside the management commands and dropping the db
manually. I personally think flush without loading fixtures (assuming
migrations will be the only way to do initial data in the future) would
not be of much use / and feels broken. I think we should be able to fake
schema migrations but still run python migrations on flush.
--
Ticket URL: <https://code.djangoproject.com/ticket/24711#comment:2>
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 django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/065.bd3d5d8cb601cf311ca115b93dd8818c%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
