#24332: Sites migration fails when DATABASES['default'] = {} ----------------------------+---------------------------------- Reporter: trecouvr | Owner: nobody Type: Bug | Status: new Component: Migrations | Version: 1.7 Severity: Normal | Keywords: migrate post_migrate Triage Stage: Unreviewed | Has patch: 0 Easy pickings: 0 | UI/UX: 0 ----------------------------+---------------------------------- 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'), } } }}} 3. 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. -- Ticket URL: <https://code.djangoproject.com/ticket/24332> 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/051.0394346cf3a08acdb18b02a29d60ad88%40djangoproject.com. For more options, visit https://groups.google.com/d/optout.