On Nov 13, 2007 11:03 AM, Peter <[EMAIL PROTECTED]> wrote: > Also, is there a big reason to override this vs the _save_FIELD_file > method as shown in this example: > http://gulopine.gamemusic.org/2007/11/customizing-filenames-without-patching.html
I'll admit, that post was thrown together in a hurry, in response to several questions that I kept answering with "it'll be better when my filestorage work makes it into trunk". I felt it was better to have something out there in the meantime, and I didn't research what solutions others had come up with. In my opinion, the FileField (or ImageField) subclass approach linked by Marcin is much simpler and cleaner than my own, and requires much less ugly hackery. That said, this should all get better when my filestorage work makes it into trunk. ;) -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 -~----------~----~----~----~------~----~------~--~---
