#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
-------------------------------------+-------------------------------------
Changes (by timgraham):
* cc: shaib (added)
Comment:
In the case of 098c07a03286b5ed133102733e67a83061647ea0, I'd expect
`allow_migrate(db, app_label)` to return `True` if any models in
`app_label` can be migrated on the database.
--
Ticket URL: <https://code.djangoproject.com/ticket/27200#comment:6>
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.e6ab9f5780054a8d85844699722c9252%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
