#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:"ba6f83ec95dbd265ae3d493c8d6375f36052d12e" ba6f83ec]:
{{{
#!CommitTicketReference repository=""
revision="ba6f83ec95dbd265ae3d493c8d6375f36052d12e"
[1.9.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:15>
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 [email protected].
To post to this group, send email to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/065.6832758e5b751a003f74d632f4a93167%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
