#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: nobody
Type: Uncategorized | Status: new
Component: Database layer | Version: 1.10
(models, ORM) |
Severity: Normal | Resolution:
Keywords: | Triage Stage:
| Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by spectras):
I don't have a use case.
I maintain a third-party package (django-hvad), that adds transparent
model translation functionalities. To ensure behavior of hvad-enabled
models is consistent with vanilla django models, I have extensive test
cases in place. That's how I detected this change.
I went through the release notes and found nothing, so I decided to open a
ticket. Documenting the change in behavior in the release notes is
perfectly fine with me. :)
--
Ticket URL: <https://code.djangoproject.com/ticket/26787#comment:4>
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.c1ed26322395a93da96345507c9f7830%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
