#23740: Cannot drop unique_together constraint on primary key
-------------------------------+--------------------------------------
     Reporter:  lanzz          |                    Owner:  nobody
         Type:  Uncategorized  |                   Status:  new
    Component:  Migrations     |                  Version:  1.7
     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 lanzz):

 Here it is:

 {{{
 Traceback (most recent call last):
   File "./bin/django", line 56, in <module>
     sys.exit(djangorecipe.manage.main('project.settings.local.foobar'))
   File "/foo/bar/eggs/djangorecipe-1.10-py2.7.egg/djangorecipe/manage.py",
 line 9, in main
     management.execute_from_command_line(sys.argv)
   File
 "/foo/bar/eggs/Django-1.7-py2.7.egg/django/core/management/__init__.py",
 line 385, in execute_from_command_line
     utility.execute()
   File
 "/foo/bar/eggs/Django-1.7-py2.7.egg/django/core/management/__init__.py",
 line 377, in execute
     self.fetch_command(subcommand).run_from_argv(self.argv)
   File
 "/foo/bar/eggs/Django-1.7-py2.7.egg/django/core/management/base.py", line
 288, in run_from_argv
     self.execute(*args, **options.__dict__)
   File
 "/foo/bar/eggs/Django-1.7-py2.7.egg/django/core/management/base.py", line
 338, in execute
     output = self.handle(*args, **options)
   File
 
"/foo/bar/eggs/Django-1.7-py2.7.egg/django/core/management/commands/migrate.py",
 line 160, in handle
     executor.migrate(targets, plan, fake=options.get("fake", False))
   File
 "/foo/bar/eggs/Django-1.7-py2.7.egg/django/db/migrations/executor.py",
 line 63, in migrate
     self.apply_migration(migration, fake=fake)
   File
 "/foo/bar/eggs/Django-1.7-py2.7.egg/django/db/migrations/executor.py",
 line 97, in apply_migration
     migration.apply(project_state, schema_editor)
   File
 "/foo/bar/eggs/Django-1.7-py2.7.egg/django/db/migrations/migration.py",
 line 107, in apply
     operation.database_forwards(self.app_label, schema_editor,
 project_state, new_state)
   File
 "/foo/bar/eggs/Django-1.7-py2.7.egg/django/db/migrations/operations/models.py",
 line 253, in database_forwards
     getattr(new_model._meta, self.option_name, set()),
   File "/foo/bar/eggs/Django-1.7-py2.7.egg/django/db/backends/schema.py",
 line 315, in alter_unique_together
     ", ".join(columns),
 ValueError: Found wrong number (2) of constraints for foo_bar(id)
 }}}

 (some identifier names and paths were changed to protect the innocent :))

--
Ticket URL: <https://code.djangoproject.com/ticket/23740#comment:2>
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/063.3ab5ec954cf70ffcb2be3e8d1363ed7c%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to