#31788: Models migration with change field foreign to many and deleting unique together. ----------------------------+--------------------------------------------- Reporter: budzichd | Owner: David Wobrock Type: Bug | Status: closed Component: Migrations | Version: 3.0 Severity: Normal | Resolution: fixed Keywords: | Triage Stage: Ready for checkin Has patch: 1 | Needs documentation: 0 Needs tests: 0 | Patch needs improvement: 0 Easy pickings: 0 | UI/UX: 0 ----------------------------+---------------------------------------------
Comment (by Mariusz Felisiak <felisiak.mariusz@…>): In [changeset:"9fce76a237ddf19e167dcba53815cbfee586b928" 9fce76a2]: {{{ #!CommitTicketReference repository="" revision="9fce76a237ddf19e167dcba53815cbfee586b928" [4.1.x] Fixed #31788 -- Fixed migration optimization after altering field to ManyToManyField. This makes AddField() used for altering to ManyToManyField, dependent on the prior RemoveField. Backport of 798b6c23ee52c675dd0f0e233c50cddd7ff15657 from main }}} -- Ticket URL: <https://code.djangoproject.com/ticket/31788#comment:9> 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 view this discussion on the web visit https://groups.google.com/d/msgid/django-updates/0107018123e645f4-7640c051-24e5-4d39-a55a-5b1a5f83eaff-000000%40eu-central-1.amazonses.com.