#16614: Support server-side cursors for queryset iteration in database backends
-------------------------------------+-------------------------------------
Reporter: toofishes | Owner:
Type: New feature | Status: new
Component: Database layer | Version: master
(models, ORM) |
Severity: Normal | Resolution:
Keywords: memory cursors | Triage Stage: Accepted
database |
Has patch: 1 | Needs documentation: 1
Needs tests: 1 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by carljm):
Technically that's not public API and we can change it if we need to, but
it does cause problems for third-party database backends (and I think
we've said that we'll mention such changes in the release notes?). So we
should only change it if it's really valuable to do so. I'm not
immediately seeing a gain in clarity from that change that would justify
it, but maybe I'm missing some subtle reason why the new name is more
accurate? Unless that's so, I'd lean towards leaving it unchanged.
--
Ticket URL: <https://code.djangoproject.com/ticket/16614#comment:19>
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/067.03f15224f5e98fbf74d8df08f3ea7bd4%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
