3 ms·
I spent some time looking at the issue today, and you may be right. I sketched out a very naive design which would be very simple but quickly grow to millions
by yalurker 17y ago
I spent some time looking at the issue today, and you may be right. I sketched out a very naive design which would be very simple but quickly grow to millions of rows, I suspect with a little research I may be able to solve it easier than I initially assumed (I'm giving myself a pre-emptive RTFM here)
What I need is to track an exercise regimen. Some issues are basic- columns for user ID, exercise ID, but I don't see how to keep track of things like number of reps & weight without growing quickly. I want to be able to log every day how many repetitions of each lift a user does and how much weight was used. Anyone spot an easy solution I'm not seeing?
- Elepsis 17y agoWhat is wrong with growing quickly? The incremental size of an additional row like you are describing is so small that you'd need thousands of users before you even noticed the disk space usage.