#26930: makemigrations tries to access default databases even when set to empty
---------------------------------+------------------------------------
Reporter: lizlemon | Owner: nobody
Type: Bug | Status: closed
Component: Migrations | Version: 1.10
Severity: Release blocker | Resolution: fixed
Keywords: | Triage Stage: Accepted
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
---------------------------------+------------------------------------
Comment (by Tim Graham <timograham@…>):
In [changeset:"ddcf7dbae7f6e5fd3c3398aba13bf55b95c80a62" ddcf7dba]:
{{{
#!CommitTicketReference repository=""
revision="ddcf7dbae7f6e5fd3c3398aba13bf55b95c80a62"
[1.10.x] Fixed #26930 -- Prevented makemigrations from accessing an empty
database.
Thanks Liz Lemon for the report and investigation and
Claude Paroz for the test.
Backport of aad46c3e370e105f9117a337924090d05f1b001d from master
}}}
--
Ticket URL: <https://code.djangoproject.com/ticket/26930#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 post to this group, send email to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/066.1b9fadce8d770e6a9ab46b2abfdcceb3%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
