On 08/05/2014 03:42 AM, Areski Belaid wrote:
> I also agree with you that custom storage will be more elegant solution.
>
> On the other hand it seems to me that reusing the same file on upload
> will not allow a clean management of user's resources, for instance if a
> user decide to delete a fil
I also agree with you that custom storage will be more elegant solution.
On the other hand it seems to me that reusing the same file on upload will
not allow a clean management of user's resources, for instance if a user
decide to delete a file we won't be able to tell if this file is used by an
It seems to me a setting is not the way to go, but a custom storage would
be better. I've made a custom storage the computes the md5 of the content
and uses that as the directory of the file, though that generate a whole
lot of directories. In a lot of ways, I think it would be great if django
Hi,
I opened a ticket suggesting to add a new setting to determine how
duplicate filename will be named:
https://code.djangoproject.com/ticket/23183
Tim asked me to bring this to the mailinglist to discuss further this
change and eventually decide if this is worth considering or if it's a no
go.
