#37060: AlterField doesn't propagate type changes through transitive
attname-based
to_field references
-------------------------------------+-------------------------------------
Reporter: Andrea Zanotto | Owner: Andrea
| Zanotto
Type: Bug | Status: closed
Component: Migrations | Version: 5.2
Severity: Normal | Resolution: fixed
Keywords: schema alterfield | Triage Stage: Ready for
to_field attname foreignkey | checkin
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by Jacob Walls <jacobtylerwalls@…>):
In [changeset:"4d455ae2d7689ce066dfffef9fc29a6f6d3ed33e" 4d455ae]:
{{{#!CommitTicketReference repository=""
revision="4d455ae2d7689ce066dfffef9fc29a6f6d3ed33e"
Refs #37060 -- Shortened app label in AlterField test for Oracle.
This avoids having to run connection.ops.truncate_name() when
deriving the table name.
Follow-up to 21c51c2623a966ba1ad8fd10e36bc8bbec93b70e.
}}}
--
Ticket URL: <https://code.djangoproject.com/ticket/37060#comment:8>
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 visit
https://groups.google.com/d/msgid/django-updates/0107019e08adf819-efa5246b-2611-4039-a748-e9e82aec7f02-000000%40eu-central-1.amazonses.com.
