I would put Prospects and Players in the same table. They are basically the same, and
I would seperate the 2 with a 'status' or a bit field that signifies whether they are
a player or not...
---------- Original Message ----------------------------------
From: "Alexander Aguilar" <[EMAIL PROTECTED]>
Reply-To: [EMAIL PROTECTED]
Date: Thu, 17 May 2001 12:41:19 -0400
I'm working on an amateur sport team's website and they of course want to keep track
of their player information. On their website they want a contact/membership form for
prospective players. Now the data that is stored for a Player and a Prospect is very
similar (personal info [height, weight, age], contact info and prowess [batting style,
specialty, experience,etc]. A prospect is not a member of the team until approved by
the team.
Initially, I was leaning toward building a Prospects table but as I mentioned the
fields are basically the same as the Player table. Now I'm thinking I should put
prospect data directly into the Player table but differentiate it by using a "status"
column which would one of the three following values (active | inactive | prospect).
My question is which is the better way to handle Prospects (ie, separate Prospect
table or use Player table with status field) ?
thanks,
alex
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Structure your ColdFusion code with Fusebox. Get the official book at
http://www.fusionauthority.com/bkinfo.cfm
Archives: http://www.mail-archive.com/[email protected]/
Unsubscribe: http://www.houseoffusion.com/index.cfm?sidebar=lists
