#29245: ForeignKeyField Renaming leads Remove and AddField instead of
RenameField
Migration
-------------------------------------+-------------------------------------
Reporter: Taqi Abbas | Owner: nobody
Type: | Status: closed
Cleanup/optimization |
Component: Migrations | Version: master
Severity: Normal | Resolution: fixed
Keywords: ForeignKey, | Triage Stage: Accepted
RenameField, db_column |
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by Tim Graham <timograham@…>):
* status: new => closed
* resolution: => fixed
Comment:
In [changeset:"2156565b5bac2e6f503ad4841e2b6ed44e4de656" 2156565b]:
{{{
#!CommitTicketReference repository=""
revision="2156565b5bac2e6f503ad4841e2b6ed44e4de656"
Fixed #29245 -- Made autodetector treat field renames + db_column addition
as RenameField.
}}}
--
Ticket URL: <https://code.djangoproject.com/ticket/29245#comment:3>
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 post to this group, send email to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/065.00070b83df68bb6f6620543332a0c922%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
