#25296: Failed Manager.create() could pollute related models cache
-------------------------------------+-------------------------------------
Reporter: rubendura | Owner:
| raphaelmerx
Type: Bug | Status: closed
Component: Database layer | Version: 1.8
(models, ORM) |
Severity: Normal | Resolution: fixed
Keywords: | Triage Stage: Accepted
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by Tim Graham <timograham@…>):
* status: assigned => closed
* resolution: => fixed
Comment:
In [changeset:"f5a33e4840d3ad4d1199e99f5a17a9af1d2176f9" f5a33e48]:
{{{
#!CommitTicketReference repository=""
revision="f5a33e4840d3ad4d1199e99f5a17a9af1d2176f9"
Fixed #25296 -- Prevented model related object cache pollution when
create() fails due to an unsaved object.
}}}
--
Ticket URL: <https://code.djangoproject.com/ticket/25296#comment:8>
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/067.2dd339a7549a229fe7b3bdf0f6546e1d%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
