Re: save() called 2 times.

Jeremy Dunck wrote: > On 5/5/06, Joseph Kocherhans <[EMAIL PROTECTED]> wrote: > ... > #Addedamorepowerfulwayofoverridingmodelmethodsremovedhardcoded_pre_save_post_saveetc. You can thank Trac for that. Apparently somebody forgot to tell them that it might be a good idea to truncate after so many

Re: save() called 2 times.

Victor : in that post it says that _post_save() is called twice, I tryed to create that _post_save() but I see nobody calls it. --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this g

Re: save() called 2 times.

On 5/5/06, Joseph Kocherhans <[EMAIL PROTECTED]> wrote: ... #Addedamorepowerfulwayofoverridingmodelmethodsremovedhardcoded_pre_save_post_saveetc. Does the Guinness book of records have an entry for "longest anchor"? ;-) --~--~-~--~~~---~--~~ You received this me

Re: save() called 2 times.

On 5/5/06, Davide Bertola <[EMAIL PROTECTED]> wrote: > > Victor : in that post it says that _post_save() is called twice, I > tryed to create that _post_save() but I see nobody calls it. _post_save is a hook method that was used before the magic-removal branch was merged. Now you just override sa

Re: save() called 2 times.

dade wrote: > In my model I have something like this : > > def Image(modes.Model): > ... > > def save(self): > print "I've been called" > ... > super(Image, self).save() > > I see in the console the print is executed 2 times when I upload the > image from the ad

Re: save() called 2 times.

yes this is a known bug. see ticket 639 http://code.djangoproject.com/ticket/639 currently I'm using an ugly work around such as def save(self): if self.imagefield : #do whetever, files does exist... also this seems to cause problems withe DateFields with auto_now... --~--~--