On 10/30/07, Ben <[EMAIL PROTECTED]> wrote: > Actually, that's given me ideas but I can't seem to work out how to do > what I want. That works by simply storing the values after the change > each time the model is updated. However, I don't seem to have both the > before and after values in a single method, they are the same before > and after the parent save() call.
Is there a particular reason you need the before and after, instead of just the after? Getting the before values would either require an additional query during your save, or you'd have to overload the __init__ method to store the original values somewhere. -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 -~----------~----~----~----~------~----~------~--~---
