I’m setting up a database to handle a FAQ page for different musical venues. The basic structure is:
id | venue_id | category | question | answer
category links to an enum table so our app can allow users to filter questions. I am trying to decide if it makes sense to use an enum table for questions since all venues will be able to answer the same (optional) questions.
Our current design shows there could be around 200 total questions. Obviously this isn’t enough to cause any type of functional issue, but I am wondering if it is logical to have an enum table this large. What are the things that I should consider when making this decision?
Additionally, if questions are tied to a category would it make sense to eliminate the category all together in lieu of the question enum or is better not to bog a enum table down with more columns than neccessary?