#23131: Potential problems with field callables copyed to migrations
-------------------------------+----------------------
Reporter: riklaunim | Owner: nobody
Type: Uncategorized | Status: new
Component: Migrations | Version: 1.7-rc-1
Severity: Normal | Keywords:
Triage Stage: Unreviewed | Has patch: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------+----------------------
Model fields support callables in few places, like:
{{{
image = models.ImageField(db_index=True, upload_to=upload_path,
blank=True)
}}}
where '''upload_path''' is a function. Migrating model with such field
will give:
{{{
('image', models.ImageField(blank=True,
upload_to=my_app.models.upload_path)),
}}}
That can easily cause problems. Future changes to the code (like different
callable name) would break old migrations (which then would break tests).
Does migrations must copy everything?
--
Ticket URL: <https://code.djangoproject.com/ticket/23131>
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/052.19504b79414f5a99aa572860ec4599e0%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
