#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:  closed
    Component:  Database layer       |                  Version:  1.9
  (models, ORM)                      |
     Severity:  Release blocker      |               Resolution:  fixed
     Keywords:                       |             Triage Stage:  Accepted
    Has patch:  1                    |      Needs documentation:  0
  Needs tests:  0                    |  Patch needs improvement:  0
Easy pickings:  0                    |                    UI/UX:  0
-------------------------------------+-------------------------------------

Comment (by Aymeric Augustin <aymeric.augustin@…>):

 In [changeset:"cfe4ba6e905eefc7e53de37226e0f342a68dc47b" cfe4ba6]:
 {{{
 #!CommitTicketReference repository=""
 revision="cfe4ba6e905eefc7e53de37226e0f342a68dc47b"
 [1.9.x] Fixed #26063 -- Crash when passing > 2000 params.

 If SQLITE_MAX_VARIABLE_NUMBER (default = 999) is changed at compile time
 to be greater than SQLITE_MAX_COLUMN (default = 2000), which Debian does
 by setting the former to 250000, Django raised an exception on queries
 containing more than 2000 parameters when DEBUG = True.

 Backport of f91b5a7e4b from master
 }}}

--
Ticket URL: <https://code.djangoproject.com/ticket/26063#comment:33>
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.5d8b2ceb7ed7d71aa09ff6946038900f%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to