One of which says (for normalization purposes) is to not store calculated data in your DB. This data is really "derived" data and can easily fall out of sync with the rest of your table.
It is always better to compute these values apart from the DB table to avoid major headaches later on.
Now I know it may be easier to store this calculated data in a field. But there really is no point in doing this. This would be similiar to storing the number of records in a table when you could just as well query the table (via the SQL count function) to get the same value. And you would not be wasting space in your table to boot.
I'm no DB expert, but I hope that helps.