[Django] #33563: Unapplying ContentType migration 0002 does not populate legacy name field on non-default database
Django
on non-default database
-------------------------------------+-------------------------------------
Reporter: Hameed | Owner: nobody
Gifford |
Type: Bug | Status: new
Component: | Version: 4.0
contrib.contenttypes |
Severity: Normal | Keywords: migrations
Triage Stage: | Has patch: 0
Unreviewed |
Needs documentation: 0 | Needs tests: 0
Patch needs improvement: 0 | Easy pickings: 0
UI/UX: 0 |
-------------------------------------+-------------------------------------
Given a database with the alias `other` that has all `contenttypes`
migrations applied, roll the state back to initial:
{{{#!bash
$ manage.py migrate --database=other contenttypes 0001
}}}
All `ContentType` rows in the `other` database will be `null` instead of
their intended value.
--
Ticket URL: <https://code.djangoproject.com/ticket/33563>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
Django
on non-default database
-------------------------------------+-------------------------------------
| Gifford
Type: Bug | Status: assigned
Component: | Version: 4.0
contrib.contenttypes |
Severity: Normal | Resolution:
Keywords: migrations | Triage Stage:
| Unreviewed
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
* owner: nobody => Hameed Gifford
* status: new => assigned
* has_patch: 0 => 1
Comment:
PR https://github.com/django/django/pull/15474
--
Ticket URL: <https://code.djangoproject.com/ticket/33563#comment:1>
Django
on non-default database
-------------------------------------+-------------------------------------
Reporter: Hameed Gifford | Owner: Hameed
| Gifford
Type: Bug | Status: assigned
Component: | Version: 4.0
contrib.contenttypes |
Severity: Normal | Resolution:
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
* stage: Unreviewed => Accepted
--
Ticket URL: <https://code.djangoproject.com/ticket/33563#comment:2>
Django
on non-default database
-------------------------------------+-------------------------------------
Reporter: Hameed Gifford | Owner: Hameed
| Gifford
Type: Bug | Status: assigned
Component: | Version: 4.0
contrib.contenttypes |
Severity: Normal | Resolution:
| checkin
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by Mariusz Felisiak):
* stage: Accepted => Ready for checkin
--
Ticket URL: <https://code.djangoproject.com/ticket/33563#comment:3>
Django
on non-default database
-------------------------------------+-------------------------------------
Reporter: Hameed Gifford | Owner: Hameed
| Gifford
Component: | Version: 4.0
contrib.contenttypes |
Severity: Normal | Resolution: fixed
Keywords: migrations | Triage Stage: Ready for
| checkin
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
* status: assigned => closed
* resolution: => fixed
Comment:
In [changeset:"58d357fc65ab0d3b16184db81059b9cef3b83c10" 58d357fc]:
{{{
#!CommitTicketReference repository=""
revision="58d357fc65ab0d3b16184db81059b9cef3b83c10"
Fixed #33563 -- Fixed contenttype reverse data migration crash with a
multiple databases setup.
}}}
--
Ticket URL: <https://code.djangoproject.com/ticket/33563#comment:4>