#26481: Add a "strict mode" for defer()/only() to prevent queries on unfetched
field access
-------------------------------------+-------------------------------------
Reporter: adamchainz | Owner: nobody
Type: New feature | Status: new
Component: Database layer | Version: master
(models, ORM) |
Severity: Normal | Resolution:
Keywords: only, defer | Triage Stage: Accepted
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by charettes):
FWIW Adrian proposed adding another keyword argument to `only()`/`defer()`
that [https://groups.google.com/forum/#!searchin/django-developers/defer
/django-developers/C3qoHEfeeUg/cwBNV5snQPMJ results in loading all
fields].
Since we might want to add different kind of actions when a deferred field
is accessed I suggest to use another name for the kwarg.
For example, we could issue a warning (`warnings.warn`) or log one
(`logging.warning`) instead of raising an exception to prevent the code
from crashing while exposing a way to monitor such instances.
--
Ticket URL: <https://code.djangoproject.com/ticket/26481#comment:3>
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/068.0803b36df0a57dc716ee8929f1640c01%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
