Ahhh... Should have said I was using magic-removal, and that this is within the admin interface.
The reason for the uuid filename is because I'm thinking of having a lot of files uploaded and I could end up with dozens of files called 'TEST.DOC' and this is one way of guaranteeing that the filename will be unique within that directory. It's based on some Zope code that works very well. We basically add the filename onto the end of the uuid and get something like cetl/3C644E61-E4EF-451E-BF03-804D9A7692D5/presentation.ppt. The file is actually stored in the filesystem using the uuid - we squirt it out as a binary stream having first set it's mimetype. Having the filename tacked on the end helps browsers to figure out what the file is and act accordingly. If Django is always going to save the file using the uploaded file name, I might have to skip uploading files using the admin interface. I should say that I do have an application where all this uuid stuff is working just fine with standard file uploads (although I've not ported that to magic removal...) Thanks for the help though Malcolm, you've saved me quite a bit of effort in digging around! Cheers, Tone --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
