#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: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
---------------------------------+------------------------------------
Comment (by timgraham):
Consulting database routers might work. I think I had rejected that
solution in mind my because I thought `model_name` was a required argument
for `allow_migrate()` but now I see it's not. I'll see if this solution is
feasible tomorrow, unless someone works on it or rejects the idea while
I'm sleeping.
--
Ticket URL: <https://code.djangoproject.com/ticket/27142#comment:5>
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.c4716d71eeb947e828e0ee25908cdc6f%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
