#12708: Django raises DoesNotExist when consulting an empty ForeignKey field
-------------------------------------+-------------------------------------
Reporter: lsaffre | Owner: nobody
Type: | Status: closed
Cleanup/optimization | Version: master
Component: Database layer | Resolution: invalid
(models, ORM) | Triage Stage:
Severity: Normal | Unreviewed
Keywords: ForeignKey | Needs documentation: 0
DoesNotExist | Patch needs improvement: 0
Has patch: 0 | UI/UX: 0
Needs tests: 0 |
Easy pickings: 0 |
-------------------------------------+-------------------------------------
Changes (by simon29):
* cc: simon@… (added)
* type: Uncategorized => Cleanup/optimization
Comment:
@lukeplant, perhaps this is something that should be cleaned up and
flagged as backward incompatible in the next major release? We ought to be
able to check the value of a field without raising an artificial error, or
resorting to workarounds.
--
Ticket URL: <https://code.djangoproject.com/ticket/12708#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 django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/065.a855a4f7a55f73e6a9d4301c7d46f535%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
