#16614: Support server-side cursors for queryset iteration in database backends
-------------------------------------+-------------------------------------
Reporter: Dan McGee | Owner: nobody
Type: New feature | Status: new
Component: Database layer | Version: 1.3
(models, ORM) |
Severity: Normal | Resolution:
Keywords: memory cursors | Triage Stage: Accepted
database |
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by Josh Smeaton):
Hi Sergey,
This is bad. Most people that use pgbouncer would be using it in
transaction mode, which makes running any query with .iterator() a
breaking change with no option to skip server side cursors. It was
actually my suggestion to transparently use server side cursors, but I
never considered the impact on something like pgbouncer.
Can you please create a new ticket for this problem, and link it back
here? I'm not sure how we'd go about making the situation right, but let's
track that discussion on the other ticket.
--
Ticket URL: <https://code.djangoproject.com/ticket/16614#comment:34>
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.5159f160b91b3308364aa47a0cea5da7%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
