Django Nose/sqlite3 "too many SQL variables" error

Trying to get started with Django nose today on an existing project, I kept getting the following error trying to run my empty test suite:

>./manage.py test --stop
Creating test database for alias 'default'...
...
django.db.utils.DatabaseError: too many SQL variables

I noticed right away that this was only happening with sqlite3 as by database. When I switched to Postgres, everything worked. Wanting my unit tests to be as fast as possible, I still wanted to use sqlite3's in memory database. I had the following in my settings.py:

if 'test' in sys.argv:
    DATABASES = {
        'default': {
            'ENGINE': 'django.db.backends.sqlite3',
            'NAME': ':memory',
        },
    }

Searching around, I didn't find anyone else with this issue. I started doing a binary search on my models to find out if one of them was the culprit, but including more than 15 or so in any combination was enough to cause the issue. Eventually I set a break point in the nose code, and walked back up the stack to Django's create_permissions manage command, which in turn called bulk_create(). Basically, Django inserts a handful of permission records for each model you define, and in this case bulk_create was trying to pass more than 999 arguments into a SQL query, which SQLite doesn't allow.

Finally, I found open Django ticket 17788. It turns out this has already been fixed, albeit not in Django 1.4.0 final. Reading that patch, I was able to come up with a couple of lines of code you can put in tests.py to work-around the issue:

# Needed to create Django permission records w/o triggering a
# "too many SQL variables" error, see: https://code.djangoproject.com/ticket/17788
from django.db.backends import sqlite3
sqlite3.base.DatabaseFeatures.can_combine_inserts_with_and_without_auto_increment_pk = False


I'm currently working at NerdWallet, a startup in San Francisco trying to bring clarity to all of life's financial decisions. We're hiring like crazy. Hit me up on Twitter, I would love to talk.

Follow @chase_seibert on Twitter