Opened 9 years ago

Closed 9 years ago

Last modified 9 years ago

#24298 closed Bug (fixed)

post-migrate handlers fail when DATABASES['default'] = {}

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

Description (last modified by Thomas Recouvreux)

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.

To reproduct the problem:

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


It seems Django tries to access the default connection. I found django.db.migrations.loader.is_latest_migration_applied uses the default connection.

I am attaching an output log of the command.
Here is a sample project to reproduce the behaviour:

Attachments (2)

migrate_failure.log (3.2 KB ) - added by Thomas Recouvreux 9 years ago.
migrate_sites_failure.log (5.5 KB ) - added by Thomas Recouvreux 9 years ago.

Download all attachments as: .zip

Change History (11)

comment:1 by Thomas Recouvreux, 9 years ago

Description: modified (diff)

by Thomas Recouvreux, 9 years ago

Attachment: migrate_failure.log added

comment:2 by Tim Graham, 9 years ago

Severity: NormalRelease blocker
Triage Stage: UnreviewedAccepted

comment:3 by Marten Kenbeek, 9 years ago

Easy pickings: set
Owner: changed from nobody to Marten Kenbeek
Status: newassigned

Seems easy enough, only 3 occurrences in the whole code-base.

comment:4 by Marten Kenbeek, 9 years ago


I'm not too sure on the tests, I'd like some feedback on that before I create a pull request.

comment:5 by Markus Holtermann, 9 years ago

Owner: changed from Marten Kenbeek to Markus Holtermann

I'm about to revert the patches for #24075.

comment:6 by Markus Holtermann, 9 years ago

Resolution: fixed
Status: assignedclosed

comment:7 by awol, 9 years ago

I think there is an additional failure scenario in the Sites application. I haven't had the chance to track down the source of the defect in Sites, in the event that I do, should I reopen this ticket or submit a new ticket?

by Thomas Recouvreux, 9 years ago

Attachment: migrate_sites_failure.log added

comment:8 by Thomas Recouvreux, 9 years ago

Thank you for the quick updates. Following the report of awol I updated my test project and added a log file. I found the problem might come from the function which calls Site.objects.exists without propagating the using parameter. I dont know either if I should create a new ticket or not.

comment:9 by Markus Holtermann, 9 years ago

Although it's a similar issue (missing use of using), it is still due to another bug. It should be Site.objects.using(using).exists() in line 20.

Please open a separate issue for that.

Note: See TracTickets for help on using tickets.
Back to Top