#27267: Renaming a primary key fails with "cannot drop constraint on table
because
other objects depend on it"
--------------------------------+--------------------------------------
Reporter: Melvyn Sopacua | Owner: nobody
Type: Bug | Status: closed
Component: Migrations | Version: 1.8
Severity: Normal | Resolution: needsinfo
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 Tim Graham):
* status: new => closed
* resolution: => needsinfo
Comment:
I created #27338 and #27339 based on issues I could find. I still don't
see steps on how to reproduce the "cannot drop constraint" error.
--
Ticket URL: <https://code.djangoproject.com/ticket/27267#comment:14>
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.798cf8d0263818e0f0628789f5650da0%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
