#12708: Django raises DoesNotExist when consulting an empty ForeignKey field
-------------------------------------+-------------------------------------
Reporter: lsaffre | Owner: nobody
Type: | Status: closed
Cleanup/optimization |
Component: Database layer | Version: master
(models, ORM) |
Severity: Normal | Resolution: invalid
Keywords: ForeignKey | Triage Stage:
DoesNotExist | Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by timgraham):
To reopen the ticket, we'd need to a proposal for how to proceed regarding
the backwards-incompatibilities. The place for that discussion is the
DevelopersMailingList. Feel free to start a thread and link to it from
here.
--
Ticket URL: <https://code.djangoproject.com/ticket/12708#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/065.9d548973c23abb9e324e5cda3afdbef3%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
