It's done more like explaining a side-effect than explaining the *purpose* of
the method. It shouldn't be "notice that when you use `exists`, it has the
following effects on efficiency", but "`exists`'s entire purpose is to get
higher efficiency in situations where you don't want to access the
On Fri, Jan 18, 2013 at 10:58 AM, Ram Rachum wrote:
> I suggest copying your explanation into the documentation.
it's already there:
" This means that calling QuerySet.exists() is faster than
bool(some_query_set), but not by a large degree. If some_query_set has
not yet been
Thanks Carl!
I suggest copying your explanation into the documentation.
Thanks,
Ram.
On Fri, Jan 18, 2013 at 5:26 PM, Carl Meyer wrote:
> Hi Ram,
>
> On 01/18/2013 06:25 AM, Ram Rachum wrote:
> > Can someone who's familiar with Django internals please confirm or deny
> >
Hi Ram,
On 01/18/2013 06:25 AM, Ram Rachum wrote:
> Can someone who's familiar with Django internals please confirm or deny
> the following answer to my question?
>
> http://stackoverflow.com/a/14369747/76701
That answer is correct. A common situation for evaluating a queryset in
a boolean
Can someone who's familiar with Django internals please confirm or deny the
following answer to my question?
http://stackoverflow.com/a/14369747/76701
Thanks,
Ram.
--
You received this message because you are subscribed to the Google Groups
"Django developers" group.
To view this discussion