#24260: Add migration support for logical field renames
-----------------------------+------------------------------------
Reporter: pennersr | Owner: nobody
Type: New feature | Status: new
Component: Migrations | Version: 1.7
Severity: Normal | Resolution:
Keywords: | Triage Stage: Accepted
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-----------------------------+------------------------------------
Comment (by timgraham):
Actually, something like simply
{{{
migrations.AlterField(
model_name='foo',
name='id',
field=models.AutoField(default=0, serialize=False, primary_key=True,
db_column=b'foo_id'),
preserve_default=False,
)
}}}
might work. Did you try that? Django needs a migration to know the field
has changed, even if no SQL is generated.
--
Ticket URL: <https://code.djangoproject.com/ticket/24260#comment:2>
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 django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/066.8c33e9231714f85df9a9694345c89f03%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
