MiKuS

I'm currently designing a golf scoring system.

now i have to store a fair bit of information i'm just wondering about the general design.

I'll have tournaments, and in tournaments there are some competitions, like nearest the pin, a, b, and c grade winner and runner up.

now is it better to have one big table for tournaments and just store every competition in that or should i use relations and have a few tables all linked together by a unique key like tournament_id?

if it helps i can provide a current tournament sheet so you can see what information needs to be stored..

Ooble

Follow normal form. If there will be duplicated data, you need to split up the table into many tables.

__________________
Me :: You :: Them