#32948: Optimise Q combination and inversion
-------------------------------------+-------------------------------------
Reporter: Keryn Knight | Owner: Keryn
Type: | Knight
Cleanup/optimization | Status: assigned
Component: Database layer | Version: dev
(models, ORM) |
Severity: Normal | Resolution:
Keywords: | Triage Stage: Accepted
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by Keryn Knight):
* has_patch: 0 => 1
Comment:
I don't ''think'' readability has been hurt by the change; I could argue
that it's been improved even, perhaps. Do judge for yourselves, naturally.
At this point there's 2 PRs to look at:
my original one: https://github.com/django/django/pull/14673
Nick P's one based on mine above:
https://github.com/django/django/pull/14677
Please note that the discussion about Nick's variant happened in-line in
my PR, as regrettably I didn't see the other PR until ''after'' we'd
started discussing the changes.
--
Ticket URL: <https://code.djangoproject.com/ticket/32948#comment:3>
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/067.8abaa17c6a9de909fc99777de9cdfe5a%40djangoproject.com.
