#25367: Allow expressions in .filter() calls
     Reporter:  Anssi Kääriäinen     |                    Owner:  Matthew
         Type:                       |  Schinckel
  Cleanup/optimization               |                   Status:  assigned
    Component:  Database layer       |                  Version:  master
  (models, ORM)                      |
     Severity:  Normal               |               Resolution:
     Keywords:                       |             Triage Stage:  Ready for
                                     |  checkin
    Has patch:  1                    |      Needs documentation:  1
  Needs tests:  0                    |  Patch needs improvement:  1
Easy pickings:  0                    |                    UI/UX:  0
Changes (by Josh Smeaton):

 * cc: josh.smeaton@… (added)
 * stage:  Accepted => Ready for checkin


 Supporting boolean expressions is enough for the framework. It will be
 possible for 3rd party libs to support more fluent syntaxes by converting
 algebraic expressions into database expressions, similar to how combinable
 works. Whether or not anyone attempts to do that is neither here nor

 I think this is a really good change. Having to annotate to filter is not
 just cumbersome, but as you've shown also a large performance hit.

 The docs might need a little bit of work, but I think the code and tests
 are fine.

Ticket URL: <https://code.djangoproject.com/ticket/25367#comment:8>
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 
For more options, visit https://groups.google.com/d/optout.

Reply via email to