#23273: MigrationRecorder does not obey db_router allow_migrate rules
----------------------------+------------------------------------
Reporter: froomzy | Owner: nobody
Type: Bug | Status: new
Component: Migrations | Version: 1.7-rc-2
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 dperetti):
Just stumbled on this issue.
With a properly written router, I expected the migrations of each app to
be executed in the right database by just using :
{{{
manage.py migrate
}}}
Could this be the behavior ?
Instead it's assuming I'm using the default database, OK, no, but ok
:-)... and it doesn't follow the allow_migrate rule and creates in the
default database the tables that are supposed to live exclusively in the
another one (NOT OK !).
So for now the workaround for me is to use a shell script where the app
and the database are specified.:
{{{
./manage.py migrate inapppurchase --database=iap
./manage.py migrate myapp --database=default
}}}
--
Ticket URL: <https://code.djangoproject.com/ticket/23273#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/065.5851a8ba1c49684d91991814bffed328%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
