#27200: router.allow_migrate without a model/hint, what is it supposed to do?
Does
it make sense to make that call?
-------------------------------------+-------------------------------------
Reporter: JBKahn | Owner: nobody
Type: Bug | Status: new
Component: Migrations | Version: 1.10
Severity: Normal | Resolution:
Keywords: makemigrations, | Triage Stage:
router, allow_migrate | Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by shaib):
c93ac9cf42bff259ab71b70a89b693b9c38e4666 was an attempt to clarify a
little the relationship between `makemigrations`, `migrate` and
`allow_migrate()`. If you can suggest how and where to add better
explanations, that could help. If you think there's a real problem here,
requiring more than a documentation fix, please explain that.
--
Ticket URL: <https://code.djangoproject.com/ticket/27200#comment:7>
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/064.26cf758638bf76ab7c82c7fc1eb3f356%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
