#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 rhertzog):

 Replying to [comment:11 aaugustin]:
 > Well we could look at the exception message. The former gives "too many
 SQL variables"; I assume the latter gives something else.
 >
 > Unfortunately I don't have access to a Debian system affected by this
 non-standard configuration right now, so I cannot reproduce the issue
 easily.

 The Debian bug report linked has the stacktrace, it ends with this:
 {{{
   File "/usr/lib/python2.7/dist-
 packages/django/db/backends/sqlite3/operations.py", line 128, in
 last_executed_query
     params = self._quote_params_for_last_executed_query(params)
   File "/usr/lib/python2.7/dist-
 packages/django/db/backends/sqlite3/operations.py", line 117, in
 _quote_params_for_last_executed_query
     return cursor.execute(sql, params).fetchone()
 OperationalError: too many columns in result set
 }}}

--
Ticket URL: <https://code.djangoproject.com/ticket/26063#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 django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/066.aab12692f148b69ff0fc35c6d62bfe4f%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to