Why to create new tables in a database
Why to create new tables in a database
Posted:20 May 2007 (20:32 UTC)I've been reading a few documents on relational databases, and they all say it is a 'good idea' to create a new table for this and that, when you decide the architecture of a new database. However, when I close the document, I never remember why to create several databases.
Maybe I'm just stupid. Let's take the example of a database for the members of a judo club. A document as mentioned above would tell me it is a 'good idea' to create a table for payments and another table for belts graduations. But why not put everything in the same table, just adding other columns?
I have asked several teachers around me, and they tell me they don't know exactly... (:twisted:) Is that the silly question nobody should ask?
Maybe I'm just stupid. Let's take the example of a database for the members of a judo club. A document as mentioned above would tell me it is a 'good idea' to create a table for payments and another table for belts graduations. But why not put everything in the same table, just adding other columns?
I have asked several teachers around me, and they tell me they don't know exactly... (:twisted:) Is that the silly question nobody should ask?
Page 1 of 1 1