#23822: Serialize model managers in migrations -----------------------------+--------------------------------------------- Reporter: MarkusH | Owner: MarkusH Type: New feature | Status: closed Component: Migrations | Version: master 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 Simon Charette <charette.s@…>): In [changeset:"4701c81df3c32d8232ed733e5848186b1da61769" 4701c81d]: {{{ #!CommitTicketReference repository="" revision="4701c81df3c32d8232ed733e5848186b1da61769" [1.8.x] Fixed #26286 -- Prevented content type managers from sharing their cache. This should prevent managers methods from returning content type instances registered to foreign apps now that these managers are also attached to models created during migration phases. Thanks Tim for the review. Refs #23822. Backport of 3938b3ccaa85f1c366909a4839696007726a09da from master }}} -- Ticket URL: <https://code.djangoproject.com/ticket/23822#comment:16> 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/065.7b75ab30aeb8ba1c84fc8e5c4b401d06%40djangoproject.com. For more options, visit https://groups.google.com/d/optout.