Hi!
Let's say I have a questions system and the writers of questions always add at least one but maybe more clues for the question.
Would it be better design to have each question have its own table for clues, even though the vast majority of the time the questions only have 1 clue? (ie is it inefficient to create like a zillion tables for a database?) Or would it be better to have a "clues" table, where each clue stores which question ID the clue applies to? (ie are later queries linear in time based on the amount of clues in the table which would be bad?)
Thanks for your help! And I'd appreciate motivations for the answers too so I will understand better.
As others have said, you want a clues table.
The clues table needs a question_id column which is obviously a foreign key linking to the id column of the questions table.
Why?
- You will have only have one clues table, not hundreds
- You can fetch all the clues for any question really easily by just retrieving all clues from the clues table with a question_id matching the id of your question
- Other less important stuff, but you can do funky things like automatically delete clues when the associated question is deleted from the questions table (using ON DELETE CASCADE or your dbs equivilant).
Definitely a clues table with an id to a question. The first idea doesn’t really make sense.
Unified clue table. It minimises repetition of data and will allow for generalisable queries later on (rather than having to rewrite queries for new questions).
I think trad database design says you should have these tables: Questions Clues Table that only links questions and clues table
Which also means you can reuse clues for different questions too
