On Tue, May 13, 2008 at 11:02 PM, Nick Retallack <[EMAIL PROTECTED]> wrote: > Currently it seems like it could be pretty disastrous to let users > upload their own files, as you can see from this ticket: > http://code.djangoproject.com/ticket/2983
I've just added a note to that ticket explaining why I left the fs-rf-docs keyword on it, but I'll reply here as well. After #5361 (my file storage refactor) lands, it'll be extremely easy to implement auto-deletion on your own, if your application needs it. The default behavior may change at some point as well, I'm not addressing that particular question. I'm just making sure that if you find your directories filling up, it will at least be possible to include auto-deletion. If a core dev wants to tell me to explicitly include auto-deletion in my next patch, I'll gladly do so. I'm just too ambivalent on the issue to take sides. > Of course, one solution is to name your files after the pk of the > record they're associated with, so new uploads will overwrite old > ones. This is a bit difficult to implement, but it's been done: > http://code.djangoproject.com/wiki/CustomUploadAndFilters #5361 will also make file naming a trivial task, so that shouldn't be a problem soon. > However, this ends up still saving this useless filename in your > database. Why bother saving something you can intuit? Ideally, I'd > like to have a model field for this that didn't even touch the > database. > > However, it chokes when I try to save the modelform, because it tries > to insert values into non-existant database columns. Somehow I also > need to tell the database cursor to ignore these fields. Either that, > or I need to find a way to reverse-engineer a model field so that it > will be acceptable in a modelform, without it attempting to insert > anything into the database. > > Some final thoughts on the matter: Oh crap -- the user could still > litter their directory with files that have different extensions -- > for example, bg.png, bg.gif, bg.jpg, bg.jpeg, etc. We may need to > implement a deleting feature after all. As you've noticed, there are definitely some concerns with doing what you're describing. Given some time and mindshare, I could probably come up with a reasonable way to approach it, but it's not much of a priority for me at the moment. If you keep at it, be sure and let the rest of us know when you find something useful, because you're not the first person I've heard make that request. -Gul --~--~---------~--~----~------------~-------~--~----~ 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?hl=en -~----------~----~----~----~------~----~------~--~---
