#35122: Migrate prune command
-------------------------------------+-------------------------------------
Reporter: smoeinbbp | Owner: nobody
Type: Bug | Status: new
Component: Core | Version: 4.2
(Management commands) |
Severity: Normal | Keywords:
Triage Stage: | Has patch: 0
Unreviewed |
Needs documentation: 0 | Needs tests: 0
Patch needs improvement: 0 | Easy pickings: 0
UI/UX: 0 |
-------------------------------------+-------------------------------------
Considering that entering the app label is mandatory when running migrate
command with --prune, it is ignored during command execution and some pre-
conditions are checked globally.
there are some apps that are actually third-party and we don't have any
control on them. if I want to prune migration only for my specific app, I
get this error:
{{{
Cannot use --prune because the following squashed migrations have their
'replaces' attributes and may not be recorded as applied:
social_django.0001_initial
social_django.0004_auto_20160423_0400
social_django.0003_alter_email_max_length
social_django.0002_add_related_name
social_django.0005_auto_20160727_2333
}}}
social_django is a third party app that I don't have any control on that.
But in prune command I used `orders` app this my app. So it seems some
preconditions are checking globally instead of checking based on app.
--
Ticket URL: <https://code.djangoproject.com/ticket/35122>
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/0107018d1c33e910-b8617667-0c55-4768-bbb6-061bdefd2e46-000000%40eu-central-1.amazonses.com.
