1 Replies - 467 Views - Last Post: 15 June 2010 - 10:31 PM Rate Topic: -----

#1 ill0pcode  Icon User is offline

  • New D.I.C Head

Reputation: 0
  • View blog
  • Posts: 2
  • Joined: 14-June 10

Normalizing a DB

Posted 14 June 2010 - 10:12 PM

I am currently working for a nonprofit start-up that a friend is doing. The program, in short, is an after school option for the local kids who are interested in playing football.

This is the list of attributes I was given that each participant will need to have...if you have experience with this or think of something else I need, please let me know.

Each player will have
name, parent name, address, phone#, cell#, email, emergency contact name, emergency number, alternate emergency number, date of birth, race, height, weight, position, shirt size, short size , pant size, school name, school city, grade level, gpa, year graduating, and planning on college (yes/no).

Parents can have multiple kids, one person can be the contact for many kids, and a school is going to have kids. So these are the tables I came up with

Parent - 1 to Many - Players
Emergency Contact - 1 to Many - Players
School - 1 to Many Players

So the Player tables loses the parent data, school data, and emergency contact. They are replaced with a parentID, schoolID, and emergencyID

Would you consider this normalized or can I take it further?

This post has been edited by ill0pcode: 15 June 2010 - 12:34 AM


Is This A Good Question/Topic? 0
  • +

Replies To: Normalizing a DB

#2 ill0pcode  Icon User is offline

  • New D.I.C Head

Reputation: 0
  • View blog
  • Posts: 2
  • Joined: 14-June 10

Re: Normalizing a DB

Posted 15 June 2010 - 10:31 PM

53 views and no feedback at all?
Was This Post Helpful? 0
  • +
  • -

Page 1 of 1