#2430: QuerySet should be evaluated when used in boolean tests
---------------------------+------------------------------------------------
Reporter: ubernostrum | Owner: mtredinnick
Status: reopened | Component: Database wrapper
Version: SVN | Resolution:
Keywords: | Stage: Accepted
Has_patch: 0 | Needs_docs: 0
Needs_tests: 0 | Needs_better_patch: 0
---------------------------+------------------------------------------------
Changes (by mtredinnick):
* status: closed => reopened
* resolution: fixed =>
* stage: Unreviewed => Accepted
Comment:
This has not been fixed, because evaluating it in the above context calls
{{{len()}}} to be called on the !QuerySet. This is a very bad idea if you
have, say, 100K rows in the result set (it reads them all into memory). We
do need to implement a proper {{{__nonzero___}}} method that only looks
for the existence of one row without consuming it (and this is only mildly
hard because the rowcount attribute on a database cursor in SQLite always
returns -1).
Reopening. I'll fix this one day. It's something that is needed.
--
Ticket URL: <http://code.djangoproject.com/ticket/2430#comment:4>
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
-~----------~----~----~----~------~----~------~--~---
