Migration squashing was always meant to be something that was useful in a rapid
development environment where you can't control all the installs (since it was
a feature developed alongside a CMS run by many clients at the time).
If you have control of all the places your project is installed
Sorry in advance of this isn’t helpful - We’ve done it successfully a few times
since 1.11… but not without a sacrifice of the virgins-in-volcano variety. Just
about any kind of RunPython command seems to get in the way. And sometimes it’s
easier to blow them all away and create fresh
I’ve never successfully squashed my migrations to any material degree, but I’ve
chalked that up to lack of doing it with any regularity. I suspect that
squashing works a lot better if you aren’t trying to clean up a mess of
hundreds of migrations files over 5 years, which is where I find
I've had similar issues. I just avoid squashing anymore. It's just not with the
pain, and having so many little files that get looked at a minimal amount of
time isn't worth fretting over. Saying that, I'd love to get it fixed...
Sent from my Verizon, Samsung Galaxy smartphone
Get Outlook for
I have a pretty big django project, and since I created the 100th migration
within one of its apps today, I thought I'd finally do some squashing. It
hasn't gone well, but I eventually got the data migrations cleaned up.
Finally, I run it, and it runs smack into a CircularDependencyError, as
anyone can help me to understandt how i can start in django, with any
tips... because in the moment when i clone the project in local i saw
commits with "hastags", for example: #123 what is the significate of this
and how can i work with that?
i am going to really appreciate yours answers
