I have the following UI:
The goal is that an organiser can enter a recurrent activity for the entire year, and the organiser can decide to select which weekdays are applicable for the recurrent event.
My database has a regular structure:
activity_id | start_date | end_date
For a one-time event, this is perfect. Even for a date range of three weeks, it's still fine.
However, for a year, it means that there can be hundreds of intervals (records) that need to be inputted into the database in a single save.
I am not confident that this is a good solution, can you give me some advice on the matter?