On 4/3/07, Malcolm Tredinnick <[EMAIL PROTECTED]> wrote: > I remember having some concerns about your approach a while back, but > apparently they weren't significant enough for me to attach a comment to > the ticket. A bit careless on my part. :-( > > I'll try to reconstruct my thinking in the background and post something > if/when I remember what was bothering me. I think it was a worry about > making this work correctly inside a model's overridden save() method, > but it's a bit fuzzy now. I'll get back to you.
I'd have major hesitations (especially a year after I first put up the patch) about it becoming the "proper" solution. I think the proper solution would involve specifying something at the model level. Possibly the ability to define a function which can dynamically determine directory names? ie. FileField(..., upload_to_function=some_func) Not really sure what the arguments to such a function would be though... This patch came out of a particular one-off use case I had, where I had one particular view that needed to do some custom upload_to work. I've always hoped that someone would come up with a better solution (after all, my patch is almost a year old), but that doesn't seem to be the case. Seems like a vital requirement for *any* site where users will be allowed to upload content. Jay P. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
