Open Jbays opened 6 years ago
For simplicity's sake, I will omit stretches from my database concerns. FOR NOW!
I'm adding to the schema -- such that workout history can be stored.
knex and postgres are definitely connected and working!
Now I'll work on further refining my database schema. Making a db to handle gymnastics progressions is tricky!
5th iteration of gymnastics-tracker ERD.
Remaining questions:
I can add stuff to my database. Everything works as expected. Below is an example.
//this adds a plank workout to my workout history INSERT INTO workouts(workout_id,timestamp,progression_id,sequence_number,step_sequence,completed,workout_note) VALUES(150,'22 september 2018',4,3,9,true,'this is a workout that I added by hand') INSERT INTO users_workouts(user_id,workout_id) VALUES(1,150)
DELETE FROM workouts where workout_id = 150; DELETE FROM users_workouts where workout_id = 150;
How to structure the table which'll contain workout history for stretches?!
I hate the names for my tables and keys.
tables: progressions_exercises_mastery mastery stretches_progressions_mastery
What's a better word than mastery? Standards? Standards table?
I need schema mockups and designs (ERD) for gymnastics tracker.
For each gymnastic progression, what data do I need to store??