* cc: bmihelac@… (added)
--
Ticket URL: <https://code.djangoproject.com/ticket/14760#comment:15>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
Comment (by bmihelac):
This pull request addresses assigning initial values for FileFields and
its subclasses:
https://github.com/django/django/pull/697
What do you think?
--
Ticket URL: <https://code.djangoproject.com/ticket/14760#comment:16>
* stage: Design decision needed => Accepted
Comment:
Moving out of DDN since it is a valid issue, the safer solution would be
to copy the file if the storage backends would allow this.
--
Ticket URL: <https://code.djangoproject.com/ticket/14760#comment:18>
* needs_better_patch: 0 => 1
* has_patch: 0 => 1
--
Ticket URL: <https://code.djangoproject.com/ticket/14760#comment:19>
Comment (by bmihelac):
timo, I can rework PR for master if it is acceptable to not copy files.
--
Ticket URL: <https://code.djangoproject.com/ticket/14760#comment:20>
Comment (by carljm):
I don't see any need to copy files here. Since we made the decision to
remove file-deletion from `FileField` entirely I think the design approach
is that a `FileField` does not "own" the file, it just references it, so
IMO there is no problem having `FileField` on multiple model instances
referencing the same file. Unless someone is doing something unusual, any
updates to any of those models will involve uploading a new file anyway,
not changing the existing one in-place.
--
Ticket URL: <https://code.djangoproject.com/ticket/14760#comment:21>
Comment (by bmihelac):
Good, I can make new PR based on this ASAP.
--
Ticket URL: <https://code.djangoproject.com/ticket/14760#comment:22>
Comment (by bmihelac):
Reworked pull request in:
https://github.com/django/django/pull/2246
--
Ticket URL: <https://code.djangoproject.com/ticket/14760#comment:23>