#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 Ryan Vennell):
Just to further confirm: I've been wrestling with this problem for a
couple days. I have multiple databases and multiple apps. When I'm running
tests, the router allow_migrate works properly to control which migrations
can be applied to which database/app.
The actual migration portion works fine, but when it comes time to
actually write the migration history, it seems to only have a concept of
the default database. When it runs ensure_schema, it's expecting that
tables should exist on the default DB when they really only exist for
certain other apps/databases. This leads to a ProgrammingError where it
can't find tables that it shouldn't be checking for in the first place.
--
Ticket URL: <https://code.djangoproject.com/ticket/23273#comment:17>
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/065.6491df94f900412825e495363884e300%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
