#35044: Accessing a deferred field clears reverse relations
-------------------------------------+-------------------------------------
Reporter: Adam Johnson | Owner: Giannis
| Terzopoulos
Type: Bug | Status: closed
Component: Database layer | Version: dev
(models, ORM) |
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
-------------------------------------+-------------------------------------
Changes (by Mariusz Felisiak <felisiak.mariusz@…>):
* resolution: => fixed
* status: assigned => closed
Comment:
In [changeset:"73df8b54a2fab53bec4c7573cda5ad8c869c2fd8" 73df8b54]:
{{{#!CommitTicketReference repository=""
revision="73df8b54a2fab53bec4c7573cda5ad8c869c2fd8"
Fixed #35044 -- Avoided clearing reverse relations and private fields when
accessing deferred fields.
Regression in a7b5ad8b19a08d7d57302ece74f6e26d2887fd9f for reverse
relations and possibly in 123b1d3fcf79f091573c40be6da7113a6ef35b62 for
private fields.
}}}
--
Ticket URL: <https://code.djangoproject.com/ticket/35044#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 [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/0107018e1dd3935b-47fbf618-868f-462b-8743-dab8737de0fe-000000%40eu-central-1.amazonses.com.
