#12708: Django raises DoesNotExist when consulting an empty ForeignKey field
-------------------------------------+-------------------------------------
Reporter: lsaffre | Owner: nobody
Type: Uncategorized | Status: closed
Component: Database layer | Version: master
(models, ORM) | Resolution: invalid
Severity: Normal | Triage Stage:
Keywords: ForeignKey | Unreviewed
DoesNotExist | Needs documentation: 0
Has patch: 0 | Patch needs improvement: 0
Needs tests: 0 | UI/UX: 0
Easy pickings: 0 |
-------------------------------------+-------------------------------------
Comment (by orshansk@…):
Incompatibilities where you check if an order has a journal by trying to
access it and checking for an exception. Unless people were proactive
(think paranoid) and also checked for None, even though it was never
allowed to be None, such a change would plainly break any and all such
checks.
--
Ticket URL: <https://code.djangoproject.com/ticket/12708#comment:5>
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/065.829e9555074cbc764b5f6feba3c19983%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
