#32083: Multiple Databases example suggest explaining migrate requires
--database
be specified for non-default
-------------------------------------+-------------------------------------
Reporter: alligatorbait | Owner: nobody
Type: | Status: new
Cleanup/optimization |
Component: Documentation | Version:
Severity: Normal | Resolution:
Keywords: migrate, multiple, | Triage Stage:
databases | Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 1 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by JamesTrick):
I believe the behaviour is documented here, under the
[https://docs.djangoproject.com/en/2.2/topics/db/multi-db/#synchronizing-
your-databases Synchronizing your databases] section. Where it says:
''The migrate management command operates on one database at a time. By
default, it operates on the default database, but by providing the
--database option, you can tell it to synchronize a different database.''
Perhaps though, we could add a line in the "An Example" section
referencing the need to specify the database? Especially since that
StackOverflow article has been viewed 13k times.
--
Ticket URL: <https://code.djangoproject.com/ticket/32083#comment:1>
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 view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/071.970fe04fc2bccc369385ba51e310d135%40djangoproject.com.
