#4399: Add __nonzero__ to allow querysets to efficiently test for emptiness
----------------------------------------------------+-----------------------
Reporter: Michael Axiak <[EMAIL PROTECTED]> | Owner:
adrian
Status: closed | Component:
Database wrapper
Version: SVN | Resolution:
duplicate
Keywords: database,performance,existence,patch | Stage:
Unreviewed
Has_patch: 1 | Needs_docs: 0
Needs_tests: 0 | Needs_better_patch: 0
----------------------------------------------------+-----------------------
Changes (by mtredinnick):
* status: new => closed
* needs_better_patch: => 0
* resolution: => duplicate
* needs_tests: => 0
* needs_docs: => 0
Comment:
Dupe of #2430.
Coincidentally, I started working on this problem (and a couple of other
len()-related problems) last night and I've got a fix that doesn't require
the extra query, using the technique at the end of that ticket.
So, thanks for the patch, but we can fix it in a way that incurs zero
extra queries. Should have something in later today or tomorrow, depending
on how much the universe hates me.
--
Ticket URL: <http://code.djangoproject.com/ticket/4399#comment:1>
Django Code <http://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 this group at
http://groups.google.com/group/django-updates?hl=en
-~----------~----~----~----~------~----~------~--~---
