#2256: queryset.count() drops LIMIT/OFFSET information
------------------------------------+---------------------------------------
Reporter: [EMAIL PROTECTED] | Owner: adrian
Status: new | Component: Database wrapper
Version: | Resolution:
Keywords: queryset count limit | Stage: Design decision
needed
Has_patch: 0 | Needs_docs: 0
Needs_tests: 0 | Needs_better_patch: 0
------------------------------------+---------------------------------------
Comment (by Collin Grady <[EMAIL PROTECTED]>):
On a whim I checked this using raw SQL and a LIMIT didn't affect the
output of COUNT, so maybe that's why the code currently drops it - not
much point adding it if the db won't respect it...
Though if there was a way to apply the limit first, and tell sql to count
those without killing performance, it would definitely be more intuitive.
--
Ticket URL: <http://code.djangoproject.com/ticket/2256#comment:9>
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
-~----------~----~----~----~------~----~------~--~---
