#27267: Migrations: Need API to drop a foreign key constraint
--------------------------------+--------------------------------------
Reporter: Melvyn Sopacua | Owner: nobody
Type: Bug | Status: new
Component: Migrations | Version: 1.8
Severity: Normal | Resolution:
Keywords: | Triage Stage: Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
--------------------------------+--------------------------------------
Comment (by Melvyn Sopacua):
I tried for a few hours to reduce it to a test case and failing. There's
something at play that I'm not considering (all relations have been setup
identical to the models in the project). So it's a corner-case, but I
can't pick what in my design is causing it. Taking a break and a fresh
look in a few days.
--
Ticket URL: <https://code.djangoproject.com/ticket/27267#comment:7>
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/072.271bf72cbb8d590f50c94453495f3208%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
