#33563: Unapplying ContentType migration 0002 does not populate legacy name
field
on non-default database
-------------------------------------+-------------------------------------
Reporter: Hameed Gifford | Owner: Hameed
| Gifford
Type: Bug | Status: closed
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
-------------------------------------+-------------------------------------
Changes (by GitHub <noreply@…>):
* 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>
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/0107017f67fb3fc7-22734c9c-1911-459a-9a9e-3296a85394d9-000000%40eu-central-1.amazonses.com.
