Changes between Initial Version and Version 5 of Ticket #30351
- Timestamp:
- 04/15/19 10:21:46 (4 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
Ticket #30351
- Property Cc Simon Charette Arthur Rio Antoine Catton added
-
Property
Component
changed from
Uncategorized
tocontrib.auth
-
Property
Summary
changed from
Migration auth.0011_update_proxy_permissions from Django 2.2 fails to apply
toMigration auth.0011_update_proxy_permissions fails for models recreated as a proxy.
-
Property
Triage Stage
changed from
Unreviewed
toAccepted
-
Property
Type
changed from
Uncategorized
toBug
-
Property
Severity
changed from
Normal
toRelease blocker
-
Ticket #30351 – Description
initial v5 1 1 I 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 (co ntent_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`. 3 3 4 4 It 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.