#27926: Allow squashmigrations to create a fresh set of migrations and delete
the
old ones
-------------------------------------+-------------------------------------
Reporter: Pascal Briet | Owner: nobody
Type: New feature | Status: new
Component: Migrations | Version: 1.10
Severity: Normal | Resolution:
Keywords: squashmigrations | Triage Stage:
| Someday/Maybe
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by Pascal Briet):
Replying to [comment:6 Sergey Yurchenko]:
> You are talking not about squashing itself but about resetting
migrations.
> I don`t think you need extra command for it. You can synchronize state
of models.py and db, remove all migrations and create new ones.
> I did it several times in large projects.
> All history is stored in your CVS
Could you please explain in details what commands you use and what file
modifications you do?
I can't see a solution without manually removing the migration history in
the DB, which is doable, but quite annoying in an automated deployment.
--
Ticket URL: <https://code.djangoproject.com/ticket/27926#comment:7>
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/064.4474b741be07c8d0ffb87eaae74505e8%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
