I am not interested in database operations
An alarming bell rang in my head. Does this mean that you also do not need to fully analyze the problem before it is implemented?
There is very different semantics associated with managing an unlimited schedule of recurring events with a well-defined pattern (for example, every Tuesday from 9-12) compared to storing a fixed schedule (for example, Tuesday, April 5, 9-12). Obviously, the latter cannot be performed with an indefinite time interval, although during a certain timeframe you can implement the former using the latter model.
If this is simply a matter of recording historical events, then the data is limited, and so the second approach is more appropriate. But for future events, you probably need both methods, but the first one is hard to implement at the database level.
source share