#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:10 aaugustin]:
> Shai: the problem in that case is that there's no way to tell apart
these two cases:
>
> - `cursor.execute()` raised `OperationalError` because
`SQLITE_MAX_VARIABLE_NUMBER = 999` (the default value) and the query
contains more than 999 parameters
> - `cursor.execute()` raised `OperationalError` while attempting to
generate the representation of the last query because of the bug reported
in this ticket
...but the statement I gave only has one column. It will never fail over
the bug, only on number of variables.
--
Ticket URL: <https://code.djangoproject.com/ticket/26063#comment:13>
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.6058ee307ef0c27bfe99ad7deb1251e9%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
