#35044: Accessing a deferred field clears reverse relations
-------------------------------------+-------------------------------------
Reporter: Adam Johnson | Owner: Giannis
| Terzopoulos
Type: Bug | Status: assigned
Component: Database layer | Version: dev
(models, ORM) |
Severity: Normal | Resolution:
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 Giannis Terzopoulos):
* owner: nobody => Giannis Terzopoulos
Comment:
Hey, I'm interested in taking this over unless @Adam, you might want to
fix this as part of #28586?
> Spotted whilst working on #28586. My implementation for that will
probably fix this issue
What I'm thinking to do is follow Simon's plan above and not clear cached
relations when `refresh_from_db(fields)` is specified, unless a relation
is part of `fields` explicitly. Not sure how I would deal with the
private fields though to be honest, or if we actually need to handle that.
--
Ticket URL: <https://code.djangoproject.com/ticket/35044#comment:2>
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/0107018d75a8e889-a8abaf97-b3f7-440f-a508-84e41315d6b1-000000%40eu-central-1.amazonses.com.
