#26787: Accessing a deleted model field attribute triggers a query to reload the
field rather than raising AttributeError (behavior change in 1.10)
-------------------------------------+-------------------------------------
Reporter: spectras | Owner: timgraham
Type: | Status: assigned
Cleanup/optimization |
Component: Documentation | Version: 1.10
Severity: Normal | Resolution:
Keywords: | Triage Stage: Accepted
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by spectras):
Great! So from the test case I understand it is guaranteed that only the
accessed field is reloaded.
I'll update my own test case to check this as well. Support for Django
v1.10 will be complete soon, thanks for being so reactive.
--
Ticket URL: <https://code.djangoproject.com/ticket/26787#comment:7>
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/066.61ba8e8b9ca940cce1ccbdc2de4af13c%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
