#26562: Introduce Storage and FileSystemStorage alternate save behaviour
-------------------------------------+-------------------------------------
Reporter: freshquiz | Owner: nobody
Type: New feature | Status: new
Component: File | Version: master
uploads/storage |
Severity: Normal | Resolution:
Keywords: file FileField | Triage Stage: Accepted
storage overwrite filepath |
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by timgraham):
Maybe I'm misunderstanding but I don't think changing the default to
overwriting files of the same name is acceptable. Allowing untrusted users
(or even trusted users, accidentally) to clobber existing files is
dangerous.
This isn't a concern if you're using a callable `FileField.upload_to` and
generating a file name instead of using the one provided by the user, but
we can't assume that.
The use case needs a bit more explanation for me to buy into the idea of
including another `Storage` class in Django.
--
Ticket URL: <https://code.djangoproject.com/ticket/26562#comment:5>
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/067.350cbf23a62353b1562ae7eef18c5800%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
