#27054: makemigrations tries to create django_migrations in external database
--------------------------------------+------------------------------------
Reporter: SydneyUniLibrary-Jim | Owner: nobody
Type: Bug | Status: new
Component: Migrations | Version: 1.10
Severity: Release blocker | Resolution:
Keywords: | Triage Stage: Accepted
Has patch: 1 | Needs documentation: 0
Needs tests: 1 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
--------------------------------------+------------------------------------
Comment (by SydneyUniLibrary-Jim):
I'm wrong about
`django.core.management.core.management.base.BaseCommand.check_migrations`
not directly or indirectly calling `applied_migrations` in the try suite.
Catching `MigrationSchemaMissing` in `applied_migrations` causes
`admin_scripts.tests.ManageRunserver.test_readonly_database` to fail. This
is because `check_migrations` no longer outputs "Not checking migrations"
and instead outputs the list of missing migrations.
Is this new behaviour of `BaseCommand.check_migrations` better?
--
Ticket URL: <https://code.djangoproject.com/ticket/27054#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/078.b6bb2a36e12057e8d119b8a60bfe0f33%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
