Is it a good/bad practice to add a boolean meaning to other fields?For instance, let's say I'm modeling events, that might be recurring or not. I can have:A boolean column that holds if the event is recurringAn integer column that holds the repetition intervalOrJust the integer column for the repetition interval, and use zero or null to indicate that the event is not recurring.The advantage of latter is that we need one field less in the table. The disadvantage that comes to my mind is that at application level is that is more clear to check if(event.isRecurring()) than if(event.getRepetitionInterval() != null).Is there a best practice in cases like this?
Should I add a boolean meaning to another column?
database;database design