Why django test --keep-db works with postgres database but not with default sqlite3

Question

I'm testing Django (v1.11.4) application in two setups of database: 1) postgres database running in docker container or 2) sqlite3 as (default database)

When running tests with --keepdb option I observe different behavior for these two setups: for postgres --keepdb works as expected (there is no database creation and running test is fast) but for sqlite3 database --keepdb seems not working (for each run of the test there is creation of database). Is it possible to have --keepdb working with sqlite3? If so any idea what settings might affect behavior described as above?

Alasdair · Accepted Answer · 2017-08-18 13:33:11Z

13

By default, Django uses an in-memory database when testing sqlite. This means that the test database isn't persistent. You can override this behaviour in your DATABASES setting by specifying a test name:

DATABASES = {
    'default': {
        'ENGINE': 'django.db.backends.sqlite',
        'NAME': 'db.sqlite3',
        'TEST': {
            'NAME': 'testdb.sqlite3',
        },
    },
}

edited Aug 18, 2017 at 13:33

answered Aug 18, 2017 at 12:36

Alasdair

310k59 gold badges605 silver badges534 bronze badges

Sign up to request clarification or add additional context in comments.

Collectives™ on Stack Overflow

Why django test --keep-db works with postgres database but not with default sqlite3

1 Answer 1

Comments

Your Answer

Hot Network Questions

Collectives™ on Stack Overflow

1 Answer 1

Comments

Your Answer

Sign up or log in

Post as a guest

Related