Re: Do people actually squash migrations?

On Wed, 12 May 2021 09:37:53 -0700 (PDT) "'Mike Lissner' via Django developers (Contributions to Django itself)" wrote: > > I haven't done the manual approach but I imagine it's something like: > > 1. Check your migrations across all apps with interdependencies for > RunPython or RunSQL

Re: Do people actually squash migrations?

On Wed, 12 May 2021 at 18:40, 'Mike Lissner' via Django developers (Contributions to Django itself) wrote: > Oh, I guess there's also a step in the manual process to reset the migrations > table in the DB, but I don't know how to do that. Tricky stuff! I've made a management command for that:

Re: Do people actually squash migrations?

Thanks for those links. I went ahead and filed a PR that describes a new "Migration Trimming" process. I'd love comments and suggestions if folks are interested and able: https://github.com/django/django/pull/14408 Mike On Mon, May 17, 2021 at 8:27 AM René Fleschenberg wrote: > Hi, > > I

Re: Do people actually squash migrations?

Hi, I agree that it would be good to extend the docs and to describe how to reset a project's migrations. Some prior art on this: https://geekchick77.dreamwidth.org/5560.html https://simpleisbetterthancomplex.com/tutorial/2016/07/26/how-to-reset-migrations.html Regards, René -- You received

Re: Do people actually squash migrations?

On Wed, May 12, 2021 at 2:50 AM 'Mike Lissner' via Django developers (Contributions to Django itself) wrote: > So, my question is: Do people actually use squashmigrations with success? For what is worth: yes. The only problem I have is a pbcak problem (I like to do esoteric things just

Re: Do people actually squash migrations?

You’d run the migrations that you manually created with --fake. My experience also corroborates the idea that squashmigrations may be unsuitable for many situation that are similar to mine, where I am able to fully control the full set of places that the code is deployed. Ryan > On May 12,

Re: Do people actually squash migrations?

Oh, I guess there's also a step in the manual process to reset the migrations table in the DB, but I don't know how to do that. Tricky stuff! On Wednesday, May 12, 2021 at 9:37:53 AM UTC-7 Mike Lissner wrote: > So sort of sounds like an update to the squash migration docs is needed if > this

Re: Do people actually squash migrations?

So sort of sounds like an update to the squash migration docs is needed if this is representative of the general sentiment. Looking at the section on this , the general outline is: 1. Overview 2. How it works 3.

Re: Do people actually squash migrations?

ia Django developers (Contributions to Django >> itself) >> *Sent:* Tuesday, May 11, 2021 7:50:31 PM >> *To:* Django developers (Contributions to Django itself) >> >> *Subject:* Do people actually squash migrations? >> >> I have a pretty big django pro

Re: Do people actually squash migrations?

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

Re: Do people actually squash migrations?

it fixed... > > Sent from my Verizon, Samsung Galaxy smartphone > Get Outlook for Android > > From: 'Mike Lissner' via Django developers (Contributions to Django itself) > > Sent: Tuesday, May 11, 2021 7:50:31 PM > To: Django developers (Contributions to Django itself) >

Re: Do people actually squash migrations?

for Android<https://aka.ms/ghei36> From: 'Mike Lissner' via Django developers (Contributions to Django itself) Sent: Tuesday, May 11, 2021 7:50:31 PM To: Django developers (Contributions to Django itself) Subject: Do people actually squash migrations?

Do people actually squash migrations?

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