On Aug 5, 12:42 am, nixlists <nixmli...@gmail.com> wrote: > On Thu, Aug 4, 2011 at 5:31 PM, Javier Guerra Giraldez > > <jav...@guerrag.com> wrote: > > On Thu, Aug 4, 2011 at 3:53 PM, nixlists <nixmli...@gmail.com> wrote: > >> What's the correct way to write the view then? Any work-arounds? > > > - collect the modified objects to a list, don't rely on the queryset > > to store them > > > or > > > - add a method to the model, as i mentioned originally. > > Thanks. I'd prefer to add a method to the model, I just don't know how > to make it find the values for fields that are in other models.
Without more informations about your models (and specially the relationships), it's going to be rather difficult. As a general consideration, if your Claim model can access these other models thru relationships, well you just have to follow the relationships. This is basic Django ORM stuff, well explained in the FineManual. -- 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 django-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/django-users?hl=en.
