#24669: Migrations should only be marked as run on "their" db
--------------------------------+--------------------
Reporter: simonpercivall | Owner: nobody
Type: Uncategorized | Status: new
Component: Migrations | Version: 1.7
Severity: Normal | Keywords:
Triage Stage: Unreviewed | Has patch: 0
Easy pickings: 0 | UI/UX: 0
--------------------------------+--------------------
We're using a multi database setup. Each db will have all migrations
written to the "django_migrations" table, even if the migration doesn't
apply to that db. Also, state is calculated for each migration, even when,
again, that migration doesn't apply.
It'd (for the writing of migrations to the db) be less confusing and
cleaner to write only applicable migrations to "django_migrations". And it
would be faster if state were to be calculated only when necessary. As it
is, building up state for all models takes a considerable amount of time
when running migrations on a "non-default" database where we only have a
few tables.
--
Ticket URL: <https://code.djangoproject.com/ticket/24669>
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/057.0d3b7b846913e4188f75c0c6c2ff9035%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
