#24332 closed Bug (fixed)
Sites migration fails when DATABASES['default'] = {}
Reported by: | Thomas Recouvreux | Owned by: | Tim Graham |
---|---|---|---|
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 (last modified by )
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:
- Create a new project
- Edit the settings.py this way:
DATABASES = { 'default': {}, 'mysite': { 'ENGINE': 'django.db.backends.sqlite3', 'NAME': os.path.join(BASE_DIR, 'db_mysite.sqlite3'), } }
- 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.
Attachments (1)
Change History (10)
by , 10 years ago
Attachment: | migrate_sites_failure.log added |
---|
comment:1 by , 10 years ago
Description: | modified (diff) |
---|
comment:2 by , 10 years ago
I am not sure if I misunderstood him or not, but I get the error reported on this ticket with branch stable/1.7.x and this is not exactly the same as mentioned in #24298. This looks like the same as #24298 but the root cause is not the same (The root cause of #24298 is the post_migrate call related to the 'auth' application whereas here the error is related to the 'sites' application).
comment:3 by , 10 years ago
Owner: | changed from | to
---|---|
Status: | new → assigned |
Triage Stage: | Unreviewed → Accepted |
Oh, I see, will look at this.
comment:4 by , 10 years ago
Description: | modified (diff) |
---|---|
Has patch: | set |
Needs tests: | set |
PR (not sure about tests at the moment)
comment:6 by , 10 years ago
Severity: | Normal → Release blocker |
---|
comment:7 by , 10 years ago
Resolution: | → fixed |
---|---|
Status: | assigned → closed |
This seems to be a duplicate of #24298 which was fixed (did you try this on the stable/1.7.x branch?). Markus asked you to open a new issue for
create_default_site()
not propagating theusing
parameter. Did you misunderstand him or am I misunderstanding you?