On Sun, 2008-10-19 at 10:21 -0700, Markos Gogoulos wrote: > hi all. When I edit an object on django admin and press save, I want > the object NOT to be saved, but instead create another object that > contains any changes (I want to be able to review it later). So the > original object has to be unchanged. I tried with this:
[...] > Now when I save an item, the other object is created, but m2m changes > are saved in my object as well. That is attributes like Charfield, > Integer field etc are not saved in the original object, but m2m > relationships are saved! > > > Any ideas on why this is happening and how I can achieve the original > object not be changed? This is probably not really possible. Many-to-many updates aren't part of the model's save() process, they're done externally. So you would need to have a way for any external caller, everywhere, to know not to use the object they have, which isn't available. It sounds like you need to intercept the "edit" flow for admin and create the new object initially, so that the user is editing the new object right from the start, rather than editing the original and then trying to hijack the final save. Regards, Malcolm --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
