#17582: DoesNotExist ambiguous exception when accessed via foreign key
-------------------------------------+-------------------------------------
     Reporter:  simon@…              |                    Owner:
         Type:                       |  JordanPowell
  Cleanup/optimization               |                   Status:  closed
    Component:  Database layer       |                  Version:  master
  (models, ORM)                      |               Resolution:  fixed
     Severity:  Normal               |             Triage Stage:  Ready for
     Keywords:                       |  checkin
    Has patch:  1                    |      Needs documentation:  0
  Needs tests:  0                    |  Patch needs improvement:  0
Easy pickings:  1                    |                    UI/UX:  0
-------------------------------------+-------------------------------------
Changes (by Tim Graham <timograham@…>):

 * status:  assigned => closed
 * resolution:   => fixed


Comment:

 In [changeset:"6f8627dd7fd482007694dd1e4a99f9e207e6d8c2"]:
 {{{
 #!CommitTicketReference repository=""
 revision="6f8627dd7fd482007694dd1e4a99f9e207e6d8c2"
 Fixed #17582 - Added message to DoesNotExist exceptions.

 Thanks simon@ for the suggestion and JordanPowell
 for the initial patch.
 }}}

-- 
Ticket URL: <https://code.djangoproject.com/ticket/17582#comment:16>
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/083.42b4990190fe713a0247a30d39826616%40djangoproject.com?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.


Reply via email to