#23749: migrations.RunPython broken with dbrouters.
-------------------------------------+-------------------------------------
Reporter: alfredperlstein | Owner: nobody
Type: Bug | Status: new
Component: Migrations | Version: 1.7
Severity: Normal | Resolution:
Keywords: migrations dbrouter | Triage Stage:
Has patch: 0 | Unreviewed
Needs tests: 0 | Needs documentation: 0
Easy pickings: 0 | Patch needs improvement: 0
| UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by splbio):
To be honest this is more like #22583.
#23273 is too complex for me to parse, there may be some overlap, but I do
not think so.
All that is needed is that we somehow pass the --database=FOO option to
the RunPython method as a kwarg so that the router can provide a function
to query that... OR that the migration itself can decide.
I am not sure why the name of the db is not given to the RunPython method.
This is a relatively simple request, can this please be fixed?
--
Ticket URL: <https://code.djangoproject.com/ticket/23749#comment:3>
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/073.26184a06e7631eab75bfd342f9299c49%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
