Yup, save() will be called whenever a model is written to the database, including through a manipulator (again, afaik)
self.name is just for example purposes. You need to change the name of the file in the ImageField or FileField object within your model. But yes, if you do this from an overloaded save() method it should change the name of the actual file (which will be written when the parent class save() method is called). Of course the only way to be sure is to try it and see. I actually have to implement something like this in the next few days; if I get something working I'll post the snippet. Cheers, ~ol On 12/14/06, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote: > > > Hi. > > Terji7 schrieb: > > Oliver Lavery wrote: > > > It seems that the most obvious way would be to alter _save_FIELD_file > in > > > django/db/models/base.py ~ line 335. > [...] > > > > That sounds like a horrible way to me. Rather use the save() method in > > the models: > > The uploaded image file is being saved by a form manipulator, not by my > implementation. > Would that also trigger my modified save method? And would just > updating self.name on the model also automagically rename the file? > > Sorry if I'm sounding ignorant here.... > > Daniel > > > > > --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
