Adding new columns to SERIES table?
While adding new age and bike handicap schemas for the 2018 Vintage Enduro Champs I started to puke at all my sparse nullable columns
Advantages of middle tables in one-to-many relationships
Should there be a separate table when mapping one to many relationship?
Disadvantages of using a nullable foreign key instead of creating an intersection table
Optimal database structure – ‘wider’ table with empty fields or greater number of tables?
Defining multiple foreign keys in one table to many tables
I think what is needed (rather than an intersection table) is to subtype EVENT (one series *could* have different event types…. seems wrong to insist that a series must consist of all the same types of event)
Then a series becomes very much about just totaling the points from the events…