On Tue, 2008-03-25 at 06:24 -0700, sector119 wrote: > My models has primary key it's 'id' field and this field is > prepopulated in Person.save() method > > def _get_id(self): > return int(str(self.pid)+str(self.location.id)) > > def save(self, raw=False): > self.id = self._get_id() > super(Person, self).save(raw=raw) > > But in: > class DeserializedObject(object): > def save(self, save_m2m=True): > models.Model.save(self.object, raw=True) > > django call models.Model.save() method not Person.save() where my > primary key is populated, and that is why primary key is None and > django doesn't use UPDATE I think...
Deserializing data is for loading data that has already been saved and serialized. So it will already have all the attributes populated (including the primary key value). We intentionally avoid calling any overridden save() methods to avoid unwanted side-effects and duplicate processing. You are using deserializing to also do some extra processing, which is not the intended use-case. If you really want to do that, it will involved subclassing the deserializer and writing your own save method on that, too. You're not just doing simple deserialization here, you're wanting to do loading *and* processing before saving, so you need to subclass the standard behaviour to do what you want. Regards, Malcolm -- Two wrongs are only the beginning. http://www.pointy-stick.com/blog/ --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
