#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 freshquiz):
A "native" `OverwritingFileSystemStorage` class would be all well and good
for file-system storage backends, but then what about other kinds of
backends (e.g. key-value cloud stores like Amazon S3)?
Half of the problem (as far as I see it), would still exist in the
`Storage.get_available_name()` method.
Please refer to #26058 for another issue which relates to my concerns
about coupling `Storage` with `FileSystemStorage`.
--
Ticket URL: <https://code.djangoproject.com/ticket/26562#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/067.36bc7e2788ec1647af49f81ffe123cf4%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
