#23273: MigrationRecorder does not obey db_router allow_migrate rules
----------------------------+------------------------------------
Reporter: froomzy | Owner: nobody
Type: Bug | Status: new
Component: Migrations | Version: master
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 marfire):
Let me amend my last comment: I think that having `migrate` blow up in
this situation would in fact solve the problem with having an inconsistent
migrations table, which is the most important thing.
My question is, since `allow_migrate()` operates at the model level and
the `migrate` command operates at the app level, wouldn't this make it
impossible to migrate some models of an app but not others?
--
Ticket URL: <https://code.djangoproject.com/ticket/23273#comment:14>
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 django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/065.895ed80b8a1a9ae3f1388431e504c1b8%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
