This week's book giveaways are in the Refactoring and Agile forums. We're giving away four copies each of Re-engineering Legacy Software and Docker in Action and have the authors on-line! See this thread and this one for details.
I am creating an application that allows you to log the days you do a particular exercise. I am using SQLite to store each Exercise in a table that has attributes such as Sets, Reps, Weight. What I am confused about is how to store the dates. I want to store the dates so that when you click View Summary of an Exercise, you will see a list of all the days that you did the exercise and how many sets, reps, and weight. To store the dates I figured I would have to add a new column to the table using ALTER command and make the date the name of the column but then that would be inefficient.
I thought about storing objects, tables, and arrays inside of SQLite but I haven't seen any finite examples, if that. I thought about storing all the attributes inside of a custom Exercise object that would then be store in internal memory but I like the idea of a database to store the info.
What is the best way to store the dates?
After doing some research I realized I could create a new table and just make a column that stores an ID of the exercise and then another column that has the dates. Then I could just perform a SELECT to get only certain exercise.