My suggestion wasn't that update_contenttypes() couldn't be modified, but rather that it might be better to expose the desired functionality as a separate utility method to avoid having to explain in the documentation how the interactive and force_remove keywords interact (probably the utility method wouldn't need to allow the user to customize either of these).
On Monday, May 25, 2015 at 2:44:28 PM UTC-4, Proto wrote: > > Original closed ticket: https://code.djangoproject.com/ticket/24820 > > The content of it is as follows: > > While removing models in one of my migrations, I was prompted by Django to >> input yes/no. For development, this is no problem. For automatic >> deployments it is. >> >> I want to know if there exists or if it's possible to add functionality >> to Django to do this. I've created a modification which works, but also >> want to learn if anyone else has solved this problem differently. >> >> Modifying the deployment file to include --noinput does not solve this >> problem (it basically defaults to no which ultimately doesn't remove the >> model). >> >> The patch I've created seems to be working just fine. My solution >> involves editing the contenttypes to take an additional argument. The >> argument can be invoked inside a migration file so that I have full control >> over when it's used. You can view the code below. >> >> Link to diff for the patch I created: >> https://github.com/Protosac/django/commit/d98fff8219469a363493e8d8455c7ffb2430d36f > > > How to use this patch: http://pastebin.com/UFr6LBAZ > > A member of the Django core team expressed interest in a solution that > would address this problem, but rejected my specific implementation above. > I wanted to open a discussion to learn how other developers were dealing > with this issue to try to come up with a better way. 100 brains are better > than one and all that :) > > Any one else encounter this problem and solve it differently? It was > recently suggested to create a Django utility module instead, which I think > is a great suggestion, but given my limited experience with the framework I > don't see how this is possible without altering `update_contenttypes` or > overriding it. It seems at some point I must intervene at that method. > -- You received this message because you are subscribed to the Google Groups "Django developers (Contributions to Django itself)" 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]. Visit this group at http://groups.google.com/group/django-developers. To view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/ac86f9ea-f6db-45bf-af33-3749389102b9%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
