Opened 10 years ago

Last modified 10 years ago

#24332 closed Bug

Sites migration fails when DATABASES['default'] = {} — at Initial Version

Reported by: Thomas Recouvreux Owned by: nobody
Component: Migrations Version: 1.7
Severity: Release blocker Keywords: migrate post_migrate
Cc: Triage Stage: Accepted
Has patch: yes Needs documentation: no
Needs tests: no Patch needs improvement: no
Easy pickings: no UI/UX: no

Description

On Django 1.7.4 the management command migrate --database=xxx fails when DATABASES['default'] = {} with django.core.exceptions.ImproperlyConfigured: settings.DATABASES is improperly configured. Please supply the ENGINE value. Check settings documentation for more details..
On Django 1.7.3 it works fine.
More details can be found on https://code.djangoproject.com/ticket/24298.

To reproduce the problem:

  1. Create a new project
  2. Edit the settings.py this way:
DATABASES = {
    'default': {},
    'mysite': {
        'ENGINE': 'django.db.backends.sqlite3',
        'NAME': os.path.join(BASE_DIR, 'db_mysite.sqlite3'),
    }
}
  1. Run python manage.py migrate --database=mysite

Problem:
It seems Django tries to access the default connection.

I am attaching an output log of the command.
Here is a sample project to reproduce the behaviour: ​https://github.com/trecouvr/test_dj_migrate_174.

Change History (1)

by Thomas Recouvreux, 10 years ago

Attachment: migrate_sites_failure.log added
Note: See TracTickets for help on using tickets.
Back to Top