#33563: Unapplying ContentType migration 0002 does not populate legacy name
field
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.
--
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 on the web visit
https://groups.google.com/d/msgid/django-updates/0107017f5e09fbb1-11cda877-a161-4b44-b7cf-62e4a8feebeb-000000%40eu-central-1.amazonses.com.
