#19895: Second iteration over an invalid queryset returns an empty list instead 
of
an exception
-------------------------------------+-------------------------------------
     Reporter:  gnosek               |                    Owner:  gnosek
         Type:  Uncategorized        |                   Status:  closed
    Component:  Database layer       |                  Version:  1.4
  (models, ORM)                      |               Resolution:  fixed
     Severity:  Normal               |             Triage Stage:
     Keywords:                       |  Unreviewed
    Has patch:  1                    |      Needs documentation:  0
  Needs tests:  0                    |  Patch needs improvement:  0
Easy pickings:  0                    |                    UI/UX:  0
-------------------------------------+-------------------------------------
Changes (by Jacob Kaplan-Moss <jacob@…>):

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


Comment:

 In [changeset:"d1e87eb3baf75b1b6a0ada46a9b77f7e347cdb60"]:
 {{{
 #!CommitTicketReference repository=""
 revision="d1e87eb3baf75b1b6a0ada46a9b77f7e347cdb60"
 [1.5.x] Fixed #19895 -- Made second iteration over invalid queryset raise
 an exception too

 When iteration over a queryset raised an exception, the result cache
 remained initialized with an empty list, so subsequent iterations returned
 an empty list instead of raising an exception

 Backport of 2cd0edaa477b327024e4007c8eaf46646dcd0f21 from master.
 }}}

-- 
Ticket URL: <https://code.djangoproject.com/ticket/19895#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].
For more options, visit https://groups.google.com/groups/opt_out.


Reply via email to