#22885: Make Query.set_limits a setter
-------------------------------------+-------------------------------------
Reporter: jorgecarleitao | Owner: nobody
Type: | Status: closed
Cleanup/optimization | Version: master
Component: Database layer | Resolution: wontfix
(models, ORM) | Triage Stage:
Severity: Normal | Unreviewed
Keywords: | Needs documentation: 0
Has patch: 0 | Patch needs improvement: 0
Needs tests: 0 | UI/UX: 0
Easy pickings: 0 |
-------------------------------------+-------------------------------------
Comment (by russellm):
Ok - but I'm still left with the question "why?"
As you've said, it's internal an internal API. Making a feature request on
an internal API doesn't make much sense to me - you must have a use case
in mind, which isn't clear at all from this ticket.
Alternatively, have you found a bug? If so, this isn't a feature request -
it's a bug report - in which case, we need to know how the bug manifests.
--
Ticket URL: <https://code.djangoproject.com/ticket/22885#comment:3>
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/072.fa0826530fd775136b2e8cab9ca427bd%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
