#16752: Multi-db without a 'default' database
-------------------------------------+-------------------------------------
Reporter: Jeremy Dunck | Owner: Ryan
| Cheley
Type: Bug | Status: assigned
Component: Database layer | Version: 1.3
(models, ORM) |
Severity: Normal | Resolution:
Keywords: | Triage Stage: Accepted
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by Ryan Cheley):
I've been poking around on this ticket and I'm not sure if the intention
here is to allow a user to specify the name of the default database, that
is allow this code to work (where `core` is ANY name other than `default`)
{{{
DATABASES = {
'core': {
'ENGINE': 'django.db.backends.sqlite3',
'NAME': BASE_DIR / 'db.sqlite3',
}
}
}}}
OR
allow the `DATABASES` setting to have an empty dictionary, that is
{{{
DATABASES = {}
}}}
and if it is set to empty, it assumes what is currently in the
`settings.py` file by default, that is
{{{
DATABASES = {
'default': {
'ENGINE': 'django.db.backends.sqlite3',
'NAME': BASE_DIR / 'db.sqlite3',
}
}
}}}
I think it's the first, but before I get too much further I wanted to add
this comment.
--
Ticket URL: <https://code.djangoproject.com/ticket/16752#comment:8>
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 [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/0107018ce087f3c9-0bb1e525-72f1-4abd-9b55-20f21e3ecc6e-000000%40eu-central-1.amazonses.com.
