#27066: Possible Memory leak while evaluating a QuerySet
-------------------------------------+-------------------------------------
Reporter: RamezIssac | Owner: nobody
Type: Uncategorized | Status: new
Component: Database layer | Version: 1.8
(models, ORM) |
Severity: Normal | Resolution:
Keywords: queryset evaluation | Triage Stage:
memory leak | Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by timgraham):
* needs_better_patch: => 0
* needs_tests: => 0
* needs_docs: => 0
Comment:
As [https://docs.djangoproject.com/en/stable/ref/models/querysets/#when-
querysets-are-evaluated the documentation says]:
Testing a `QuerySet` in a boolean context, such as using `bool()`, `or`,
`and` or an `if` statement, will cause the query to be executed. If there
is at least one result, the `QuerySet` is `True`, otherwise `False`. If
you only want to determine if at least one result exists (and don’t need
the actual objects), it’s more efficient to use `exists()`.
Can you provide more details if that doesn't address your concerns?
--
Ticket URL: <https://code.djangoproject.com/ticket/27066#comment:1>
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 post to this group, send email to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/068.8dfc40e65babeded54a0179a838d9ff7%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
