#26063: Regression in Django 1.9: SQLite can no longer handle more than 2000
values
in a "foo__in" filter
-------------------------------------+-------------------------------------
Reporter: rhertzog | Owner: aaugustin
Type: Bug | Status: assigned
Component: Database layer | Version: 1.9
(models, ORM) |
Severity: Release blocker | Resolution:
Keywords: | Triage Stage: Accepted
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 1
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by shaib):
Replying to [comment:20 aaugustin]:
> Shai: exactly — that's why we can't tell an `OperationalError` when
running the query because P > SQLITE_MAX_VARIABLE_NUMBER from an
`OperationalError` while quoting the params because P > SQLITE_MAX_COLUMN,
which in turn is why I ended up testing the private API that does just the
quoting.
We can if we run the "big P, small C" query on a raw cursor rather than a
Django cursor.
--
Ticket URL: <https://code.djangoproject.com/ticket/26063#comment:27>
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/066.976b82e76b6c23ab6e78fac1de59b955%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
