I have two entity's - Workout and Exercise. These will have a 'many-to-many' (M:N) relationship through the junction table WorkoutExercise. Things start to get complicated when I need to have a 'one-to-many' (1:M) relationship on this table from the table called Sets.
I have provided the entity-relationship diagram below to help illustrate the scenario:
Is this poor design? i.e. is it bad for performance? is there a better way?