#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: 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 Tim Graham):
I'm not sure how changing a `CharField` primary key to an `AutoField`
primary key should work (is it possible to autopopulate the column using
the sequence?), but the current behavior of prompting for a default then
erring with "multiple default values specified for column "character_id"
of table "t27267_foo"" isn't good. I guess we could open a separate ticket
for this issue. I'm not sure what else could be done with the information
you provided.
--
Ticket URL: <https://code.djangoproject.com/ticket/27267#comment:13>
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.a2e08fbba1a3b7f7c924c0b3eba0cd60%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
