Hi all, I had a previous post on this issue which I did not get very many answers to. In particular, I did not have many responses those who may be more directly involved with the development of this great Framework (or maybe more appropriately the Admin extension of it? which is such a feature that for all practical purposes it may well be seen as core to the Framework.)
The default behaviour is for Admin not to overwrite a file with a newer one posted with the same name, i.e. if I upload a file called ycoci.jpg to a folder which contains an older version of the same file, the newer one will be renamed wthin an underscore,ycoci_.jpg. I would like to know why this is handled in this way, as find it very unintuitive (There many well be a very valid reason for handling things in this way? However, it seems to me that the natural thing to do is to rename the older file with the underscore then delete it, before posting the newer file with the original name). I have developed a very workable web project with Django 0.91, but this behaviour is causing me real grief, as I now have loads of files on disc that are not being used, which is a huge waste of disc space and one part of my project depends on files preserving their names. I would be grateful for any suggestions as to how I can get around this limitation. Thanks and Best, Y-coci --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-users -~----------~----~----~----~------~----~------~--~---
