#22583: Allow per-database migrations in multidb configurations
-----------------------------+------------------------------------
Reporter: akaariai | Owner: nobody
Type: New feature | 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 andrewgodwin):
So, it's worth pointing out that RunPython can just switch on the value of
`schema_editor.connection` if it wants to make decisions about the current
database, so I'm not sure if I want to add extra logic to RunSQL?
Especially a run-per-backend thing...
--
Ticket URL: <https://code.djangoproject.com/ticket/22583#comment:2>
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/066.13539825777fc50d0cae4b24cacc4585%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
