#34298: drop constraint if exists
-------------------------------------+-------------------------------------
Reporter: sahaliyev | Owner: nobody
Type: New feature | Status: closed
Component: Core (Management | Version: 4.1
commands) |
Severity: Normal | Resolution: wontfix
Keywords: | Triage Stage:
| Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by Mariusz Felisiak):
* status: new => closed
* resolution: => wontfix
Comment:
Thanks for this ticket, however when you mix manual changes to your
database schema and Django migrations you do it at your own risk. You can
always use the `--fake` option to mark a migration as already applied.
> It would be great just try to drop constraint and if not exists just
pass.
I disagree. The migrations framework should fail loudly when it encounters
an unexpected database state.
--
Ticket URL: <https://code.djangoproject.com/ticket/34298#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/01070185f2d782e1-a115cb79-2950-446d-aca5-c1dd47b6bab4-000000%40eu-central-1.amazonses.com.
