Re: adding a summary field to a model

You replied faster than me Mathieu :)
It looks the easiest solution unless the SUM is potentially heavy on
the system...
There are of course other means to circumvent the issue but it going
further & further in the denormalization process (it is not an issue
per se ... you just have to be aware of it).

\T,

On Aug 19, 5:47 pm, Mathieu Leduc-Hamel <marra...@gmail.com> wrote:
> But by the way you field seem to be a sum of some others, maybe it should
> not be a new field but just a new method returing the resulting calculation
> depending of the attributes of your instance. No ?
>
> On Thu, Aug 19, 2010 at 4:56 PM, bruno desthuilliers <
>
> bruno.desthuilli...@gmail.com> wrote:
> > On 19 août, 16:25, Nick <nickt...@gmail.com> wrote:
> > > You need to look at overriding the model's save method in order to add
> > > data from one field to another dynamically.
>
> > Useless denormalization (until proved otherwise of course...).
>
> > --
> > 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+unsubscribe@googlegroups.com<django-users%2Bunsubscribe@googlegroups.com>
> > .
> > For more options, visit this group at
> >http://groups.google.com/group/django-users?hl=en.

--
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+unsubscribe@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/django-users?hl=en.