#33598: Using multiple FilteredRelation with different filters but for same
relation is ignored.
-------------------------------------+-------------------------------------
     Reporter:  lind-marcus          |                    Owner:  Mariusz
                                     |  Felisiak
         Type:  Bug                  |                   Status:  closed
    Component:  Database layer       |                  Version:  4.0
  (models, ORM)                      |
     Severity:  Release blocker      |               Resolution:  fixed
     Keywords:  FilteredRelation     |             Triage Stage:  Ready for
                                     |  checkin
    Has patch:  1                    |      Needs documentation:  0
  Needs tests:  0                    |  Patch needs improvement:  0
Easy pickings:  0                    |                    UI/UX:  0
-------------------------------------+-------------------------------------

Comment (by Mariusz Felisiak <felisiak.mariusz@…>):

 In [changeset:"7d540d67a8fb17f820e1657ccb1509af86b27582" 7d540d67]:
 {{{
 #!CommitTicketReference repository=""
 revision="7d540d67a8fb17f820e1657ccb1509af86b27582"
 [4.0.x] Fixed #33598 -- Reverted "Removed unnecessary
 reuse_with_filtered_relation argument from Query methods."

 Thanks lind-marcus for the report.

 This reverts commit 0c71e0f9cfa714a22297ad31dd5613ee548db379.

 Regression in 0c71e0f9cfa714a22297ad31dd5613ee548db379.
 Backport of fac662f4798f7e4e0ed9be6b4fb4a87a80810a68 from main
 }}}

-- 
Ticket URL: <https://code.djangoproject.com/ticket/33598#comment:7>
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/0107017fd9507df2-d99e4745-b4c0-40eb-8d8d-5e9991a9965a-000000%40eu-central-1.amazonses.com.

Reply via email to