#27142: makemigrations fails on special database connections
---------------------------------+------------------------------------
Reporter: gerricom | 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: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
---------------------------------+------------------------------------
Comment (by gerricom):
Replying to [comment:11 timgraham]:
> Some tests are added and the patch might be ready for review,
This works fine for my case.
Replying to [comment:11 timgraham]:
> For example, a project with a read-only database that defines some
database routers but hasn't setup a router to prevent migrating on the
read-only database will need to add a rule in a router's allow_migrate()
to prevent the consistency check.
But I believe this is a good solution as you would have most likely set up
a database router for your read-only database.
--
Ticket URL: <https://code.djangoproject.com/ticket/27142#comment:12>
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.bb14ab63a5a3f752bc2e1265706fe397%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
