Opened 4 years ago

Closed 4 years ago

#33563 closed Bug (fixed)

Unapplying ContentType migration 0002 does not populate legacy name field on non-default database

Reported by: Hameed Gifford Owned by: Hameed Gifford
Component: contrib.contenttypes Version: 4.0
Severity: Normal Keywords: migrations
Cc: Triage Stage: Ready for checkin
Has patch: yes Needs documentation: no
Needs tests: no Patch needs improvement: no
Easy pickings: no UI/UX: no

Description

Given a database with the alias other that has all contenttypes migrations applied, roll the state back to initial:

$ manage.py migrate --database=other contenttypes 0001

All ContentType rows in the other database will be null instead of their intended value.

Change History (4)

comment:1 by Hameed Gifford, 4 years ago

Has patch: set
Owner: changed from nobody to Hameed Gifford
Status: new → assigned

PR ​https://github.com/django/django/pull/15474

comment:2 by Mariusz Felisiak, 4 years ago

Triage Stage: Unreviewed → Accepted

comment:3 by Mariusz Felisiak, 4 years ago

Triage Stage: Accepted → Ready for checkin

comment:4 by GitHub <noreply@…>, 4 years ago

Resolution: → fixed
Status: assigned → closed

In 58d357fc:

Fixed #33563 -- Fixed contenttype reverse data migration crash with a multiple databases setup.

Note: See TracTickets for help on using tickets.
Back to Top