#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: closed
Cleanup/optimization |
Component: Documentation | Version: 1.10
Severity: Normal | Resolution: fixed
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 Tim Graham <timograham@…>):
In [changeset:"45a650777e4674bc540c3bf4b3108409f0e1f98a" 45a6507]:
{{{
#!CommitTicketReference repository=""
revision="45a650777e4674bc540c3bf4b3108409f0e1f98a"
[1.10.x] Fixed #26787 -- Documented deleting and reloading of model
instance fields.
Thanks Julien Hartmann for the report.
Backport of 20d1cb33c2ec1242e16c49deb88e8c70517b2d1a from master
}}}
--
Ticket URL: <https://code.djangoproject.com/ticket/26787#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 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.d4bad57a0ec24be8c82b7669205ae99c%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.