#10790: Too many joins in a comparison for NULL.
-------------------------------------+-------------------------------------
     Reporter:  mtredinnick          |                    Owner:  akaariai
         Type:  Bug                  |                   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:  0                    |                    UI/UX:  0
-------------------------------------+-------------------------------------
Changes (by Anssi Kääriäinen <akaariai@…>):

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


Comment:

 In [changeset:"69597e5bcc89aadafd1b76abf7efab30ee0b8b1a"]:
 {{{
 #!CommitTicketReference repository=""
 revision="69597e5bcc89aadafd1b76abf7efab30ee0b8b1a"
 Fixed #10790 -- Refactored sql.Query.setup_joins()

 This is a rather large refactoring. The "lookup traversal" code was
 splitted out from the setup_joins. There is now names_to_path() method
 which does the lookup traveling, the actual work of setup_joins() is
 calling names_to_path() and then adding the joins found into the query.

 As a side effect it was possible to remove the "process_extra"
 functionality used by genric relations. This never worked for left
 joins. Now the extra restriction is appended directly to the join
 condition instead of the where clause.

 To generate the extra condition we need to have the join field
 available in the compiler. This has the side-effect that we need more
 ugly code in Query.__getstate__ and __setstate__ as Field objects
 aren't pickleable.

 The join trimming code got a big change - now we trim all direct joins
 and never trim reverse joins. This also fixes the problem in #10790
 which was join trimming in null filter cases.
 }}}

-- 
Ticket URL: <https://code.djangoproject.com/ticket/10790#comment:51>
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 post to this group, send email to [email protected].
To unsubscribe from this group, send email to 
[email protected].
For more options, visit https://groups.google.com/groups/opt_out.


Reply via email to