Join GitHub today
GitHub is home to over 36 million developers working together to host and review code, manage projects, and build software together.Sign up
Fixed hr/pace zones for long-term analysis #1726
How should these values be saved in database?
The last solution would (currently) fix the number of levels - and that's done anyway. And although it looks ugly and is not normalized, it may be the best in terms of performance. Every time values are inserted/updated/deleted, we will touch the whole set of values for one activity.
Still see #1151. (This one could be declared as a duplicate, I just wanted to sum up what we've discussed so far.)
In addition, definitions for these zones and respective limits should not be overcomplicated. Long-term analysis is thought to give the 'big picture' of long-term changes in one's training. It does not matter that much whether a zone ends at 4:00/km or 4:05/km (or at 90%HRmax or 92%HRmax). It's just important to use enough zones.