#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 Melvyn Sopacua):
One step closer: the default in the column definition doesn't contain the
Nextval() function for the serial. So two weird points:
1. Django prompts for missing default and given that the Nextval() for the
serial isn't being picked up this seems logical
2. When a default is specified, suddenly psychopg2 complains about two
defaults, so between that check and the SQL backend a default value is
inserted *but* doesn't end up in the table definition.
--
Ticket URL: <https://code.djangoproject.com/ticket/27267#comment:10>
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 django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/072.c11a735bb47ca3998cdb5bb429005f49%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
