I'm designing a personal database that has a table which contains categories for seasonal events of a video game. In my design I have a related column from
Items (one to many [1:m] respectively). However, whenever there is no event/season going on, I'm not sure whether I should create an special row in my
Events table to handle such scenarios or just leave the related column of
I've been researching about the topic and I have several found reasonable arguments for either case (to use or not to use a null), but the problem is that none of what I've read so far is framed in use-case that would apply for my specific dilemma. As a result, I'm now even more confused as to what to do. I was originally going to add a "Non-Event" row to my table.