#24368: FileField needlessly serializes upload_to
-------------------------------+--------------------------------------
Reporter: rdaysky | Owner: nobody
Type: Uncategorized | Status: closed
Component: Migrations | Version: 1.7
Severity: Normal | Resolution: wontfix
Keywords: | Triage Stage: Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------+--------------------------------------
Changes (by timgraham):
* status: new => closed
* resolution: => wontfix
Comment:
The documentation describes why options like `upload_to` are serialized:
Django will make migrations for any change to your models or fields -
even options that don’t affect the database - as the only way it can
reconstruct a field correctly is to have all the changes in the history,
and you might need those options in some data migrations later on (for
example, if you’ve set custom validators).
I'm not convinced that allowing lambdas for some options where it may not
be needed (like `upload_to`), but not in other places where it is needed
(like `default`) would be a good situation. Could you please raise the
issue on the DevelopersMailingList if you think it merits further
discussion? Thank-you.
--
Ticket URL: <https://code.djangoproject.com/ticket/24368#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.cdde1ffea913530722c4e216beb1bf35%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
