Changes between Initial Version and Version 5 of Ticket #30351


Ignore:
Timestamp:
04/15/2019 05:21:46 AM (8 months ago)
Author:
felixxm
Comment:

Legend:

Unmodified
Added
Removed
Modified
  • Ticket #30351

    • Property Cc Simon Charette Arthur Rio Antoine Catton added
    • Property Component changed from Uncategorized to contrib.auth
    • Property Summary changed from Migration auth.0011_update_proxy_permissions from Django 2.2 fails to apply to Migration auth.0011_update_proxy_permissions fails for models recreated as a proxy.
    • Property Triage Stage changed from Unreviewed to Accepted
    • Property Type changed from Uncategorized to Bug
    • Property Severity changed from Normal to Release blocker
  • Ticket #30351 – Description

    initial v5  
    11I am trying to update my project to Django 2.2. When I launch `python manage.py migrate`, I get this error message when migration `auth.0011_update_proxy_permissions` is applying (full stacktrace is available [https://dpaste.de/5nJJ here]):
    2 `django.db.utils.IntegrityError: duplicate key value violates unique constraint "idx_18141_auth_permission_content_type_id_01ab375a_uniq" DETAIL:  Key (content_type_id, codename)=(12, add_agency) already exists`.
     2`django.db.utils.IntegrityError: duplicate key value violates unique constraint "idx_18141_auth_permission_content_type_id_01ab375a_uniq" DETAIL:  Key (co.ntent_type_id, codename)=(12, add_agency) already exists`.
    33
    44It looks like the migration is trying to re-create already existing entries in the `auth_permission` table. At first I though it cloud because we recently renamed a model. But after digging and deleting the entries associated with the renamed model from our database in the `auth_permission` table, the problem still occurs with other proxy models.
Back to Top