#33563: Unapplying ContentType migration 0002 does not populate legacy name
field
on non-default database
-------------------------------------+-------------------------------------
Reporter: Hameed Gifford | Owner: Hameed
| 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
-------------------------------------+-------------------------------------
Changes (by Hameed Gifford):
* 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 <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/0107017f5e0f88dd-519b4daa-3710-41b8-8b1d-9526ffe75ee9-000000%40eu-central-1.amazonses.com.
