I'd recommend a prospects table just so that your player table which will
get hit more often from the site will be as lean as possible. Upon approval
I'd have a query copy the data into the players table and delete the data in
the prospects table..
J.
John Wilker
Web Applications Consultant
Macromedia Certified ColdFusion Developer
www.red-omega.com <http://www.red-omega.com>
"Losing - If at first you don't succeed, failure may be your style."
~despair.com
-----Original Message-----
From: Alexander Aguilar [mailto:[EMAIL PROTECTED]]
Sent: Thursday, May 17, 2001 9:41 AM
To: CF-Talk
Subject: OT: database modeling
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
