database/tables

[jomuir]

I have just created my first set of tables (normally import or connect to a DB) - I believe I have setup correctly with normalisation etc but not sure. I have created a DB for a bunch of us that play golf once a year, and play at different places, different people can attend, handicaps change everyday, number of times your ball goes in water (soup), penalty can be added at end of round (alters following day handicap)....anyway the tables and links are shown below.

Does this look correct or have I made mistakes? Can upload a test access db if required.

 

[rzw0wr]

Good start.
If I understand golf then the "order" would be;
Players play courses, Courses have Holes, Holes have Scores.
Courses have Tournaments, Tournaments have rounds.
Lay it out like it actually happens in this case.
Example, the Main attributes of courses is holes.

BTW, when I see a relationships that made a circle I start to wonder.
EDIT:
Tip, remember when making a relationship that you can not enter a value (data) into the Many table until the 1 table has an enter. This may help you understand in what table the FK id belongs.
Dale

 

[gemma-the-husky]

i did one of these a few years ago, but I can't put my hands on it.

this is a wonderful project for a first database to be honest. complex enough to be interesting, but still relatively simple, and contained.

it looks pretty close, I think. The multi-round tournament structure makes it rather more complicated.

in the players score for each hole in the round, you may want to build in the adjusted score taking into account the handicap, and the stableford points if applicable. This may be considered duplication of data, but it may be helpful to have it available.

 

[jomuir]

Thank you for the feedback, so looking at it from your order suggestion:

Competitors play in tournaments
tournaments have rounds
rounds played on a course
course have holes
holes have scores......not sure how this would be tied in to the competitor without a circle/loop?

 

[RainLover]

Year, Date, Round, Day and Name are all reserved words and can cause programing faults..

Suggest you use something different like MyName etc.

You can do a Google search for reserved words.

 

[gemma-the-husky]

Thank you for the feedback, so looking at it from your order suggestion:

Competitors play in tournaments
tournaments have rounds
rounds played on a course
course have holes
holes have scores......not sure how this would be tied in to the competitor without a circle/loop?

maybe this

"permanent" course data

(even this is tricky though because holes/courses do get redesigned, and a par 4 can become a par 5, say)

club table (St Andrews, Wentworth)
course table (some clubs have several courses)
holes tables (1-18) on each course

"players" details

players table
rounds table (player - course)
round-holes table (rounds - holes)


"tournament" details

tournament
competitors (tournament - players)


further complications then arise when you consider tournaments, as tournaments are going to consist of a number of particular rounds for a set of players.

maybe all you need is to record a "round" as being part of a given tournament. "casual rounds" can then just be free-standing, if you will and not linked to a tournament.

the best way is to try something going roughly the right way, see where it takes you, and refine it as required.