#29755: Infinite migrations created after removing Meta.default_related_name -------------------------------------+------------------------------------- Reporter: Aamir Rind | Owner: Simon | Charette Type: Bug | Status: closed Component: Migrations | Version: 1.11 Severity: Normal | Resolution: fixed Keywords: | Triage Stage: Ready for migrations,unlimited,infinite,makemigrations| checkin Has patch: 1 | Needs documentation: 0 Needs tests: 0 | Patch needs improvement: 0 Easy pickings: 0 | UI/UX: 0 -------------------------------------+-------------------------------------
Comment (by Tim Graham <timograham@…>): In [changeset:"4c5a8c6f50577daa8b8aaef28a8f32ab34185e80" 4c5a8c6]: {{{ #!CommitTicketReference repository="" revision="4c5a8c6f50577daa8b8aaef28a8f32ab34185e80" [2.1.x] Fixed #29755 -- Made migrations detect changes to Meta.default_related_name. Backport of a4495f4b989dc919d80fcf9f38e31e247faa94fb from master }}} -- Ticket URL: <https://code.djangoproject.com/ticket/29755#comment:5> 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/070.fe309ddd3b6a5e3b6298852cfc963d38%40djangoproject.com. For more options, visit https://groups.google.com/d/optout.