A question is how difficult are the calculations? For example, do they take longer to do than it takes for the extra data to serialized by the database, transmitted over the DB socket by the database, received by the Django DB connection socket, and for Django to deserialize them? If not, then storing the results is a false economy.
Saving the calculated values to the database is also a database denormalization. You will likely be forever finding bugs where the calculation didn't change when you changed a piece of data it was based upon. By the way, Python properties (they are not at all Django specific) are little more than syntactic sugar on top of methods (a useful exception being the ability to make them read only, where storing to a method name can give surprising results). Properties are fine, but you may find your code more readable six months down the road if you just use methods. Bill On Tue, Mar 12, 2013 at 9:41 AM, Doug S <webcoach...@gmail.com> wrote: > Thanks for the quick replies. > Straight fields it is, that makes things simple. > > -- > You received this message because you are subscribed to the Google Groups > "Django users" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to django-users+unsubscr...@googlegroups.com. > To post to this group, send email to django-users@googlegroups.com. > Visit this group at http://groups.google.com/group/django-users?hl=en. > For more options, visit https://groups.google.com/groups/opt_out. > > > -- You received this message because you are subscribed to the Google Groups "Django users" group. To unsubscribe from this group and stop receiving emails from it, send an email to django-users+unsubscr...@googlegroups.com. To post to this group, send email to django-users@googlegroups.com. Visit this group at http://groups.google.com/group/django-users?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
