• Some users have recently had their accounts hijacked. It seems that the now defunct EVGA forums might have compromised your password there and seems many are using the same PW here. We would suggest you UPDATE YOUR PASSWORD and TURN ON 2FA for your account here to further secure it. None of the compromised accounts had 2FA turned on.
    Once you have enabled 2FA, your account will be updated soon to show a badge, letting other members know that you use 2FA to protect your account. This should be beneficial for everyone that uses FSFT.

normailization question

Burnsy

Limp Gawd
Joined
Jul 1, 2001
Messages
440
my teacher gave us this assingment to normalize

golfersscores table
(memID, date, time, score, hanicap, address, phone, golfcourseID, courserating, courseslope)

we need to to split this up into different tables

the problem im having is that i made a tee time table as the intersection table between golfcourse and golfers

my question is should i make another field (ex teetimeID) as the primary key, or use memid, date and time as 3 primary keys?>
 
If you have a tee time table then you want to have teetimeID to identify the record in the table. Each record needs a unique key.
 
doesnt the combination of date, time and memID combine at one to make a unique key or no?
 
You really dont want to start making compound keys becuase you will have problems querying that date. It is more efficient to add another column and make a unique single key.
 
Back
Top