#27892: Independent migrations
----------------------------------------+------------------------------
Reporter: ChillarAnand | Owner: ChillarAnand
Type: New feature | Status: assigned
Component: Migrations | Version: master
Severity: Normal | Keywords:
Triage Stage: Unreviewed | Has patch: 0
Needs documentation: 0 | Needs tests: 0
Patch needs improvement: 0 | Easy pickings: 0
UI/UX: 0 |
----------------------------------------+------------------------------
Currently django uses MigrationGraph and decides the order of migrations
before applying them. When writing migrations manually, users should
specify `dependencies` or `run_before` for a migration so that django can
decide when to apply it.
This becomes a problem with independent migrations like this
{{{
from django.contrib.postgres.operations import UnaccentExtension
from django.db import migrations
class Migration(migrations.Migration):
operations = [
UnaccentExtension(),
]
}}}
Is it possible to have `independent` field on `Migration` class, so that
these migrations will be applied first then django can resume with
migrations as usual.
--
Ticket URL: <https://code.djangoproject.com/ticket/27892>
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/055.73f8f370c80cbc296a57aa876996e324%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
