#13349 closed (fixed)
Raw Queries with backends that don't support chunked reads aren't done correctly
| Reported by: | Alex Gaynor | Owned by: | nobody |
|---|---|---|---|
| Component: | Database layer (models, ORM) | Version: | dev |
| Severity: | Keywords: | ||
| Cc: | Triage Stage: | Accepted | |
| Has patch: | yes | Needs documentation: | no |
| Needs tests: | no | Patch needs improvement: | no |
| Easy pickings: | no | UI/UX: | no |
Description
If a backend doesn't support chunked reads the cursor should be exhausted immediately. This leads to bugs in PyPy, and probably other non-cpython systems.
Attachments (1)
Change History (4)
by , 15 years ago
| Attachment: | django-raw-cursor.diff added |
|---|
comment:1 by , 15 years ago
| Triage Stage: | Unreviewed → Accepted |
|---|
comment:2 by , 15 years ago
| Resolution: | → fixed |
|---|---|
| Status: | new → closed |
Note:
See TracTickets
for help on using tickets.
(In [12978]) Fixed #13349 -- Ensure that raw queries evaluate the entire query if the backend doesn't support chunked reads. Thanks to Alex Gaynor for the report and patch.