#36839: Renaming of content types on RenameModel operations silently passes when
duplicates are found
-------------------------------------+-------------------------------------
Reporter: Jacob Walls | Owner: Moksha
| Choksi
Type: Bug | Status: new
Component: | Version: 6.0
contrib.contenttypes |
Severity: Normal | Resolution:
Keywords: | Triage Stage: Accepted
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by Natalia Bidart):
* stage: Unreviewed => Accepted
Comment:
Thank you Jacob, with these instructions I was able to reproduce. Not only
the data did not migrate, but the old content type was left behind:
{{{#!sql
django=# SELECT * FROM django_content_type WHERE app_label =
'ticket_36839';
id | app_label | model
----+--------------+------------
65 | ticket_36839 | melody
66 | ticket_36839 | song
67 | ticket_36839 | taggedsong
(3 rows)
django=# SELECT * FROM ticket_36839_taggedsong;
id | tag | object_id | content_type_id
----+-----+-----------+-----------------
1 | hit | 1 | 66
(1 row)
}}}
--
Ticket URL: <https://code.djangoproject.com/ticket/36839#comment:8>
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 view this discussion visit
https://groups.google.com/d/msgid/django-updates/0107019bbf54be0b-15b0156f-06d2-4a0e-a98f-b20e46ae332d-000000%40eu-central-1.amazonses.com.
