Personally i would make a series of tables to deal with this type of information that
ties back to each user via Primary Key identifier....
like this
Table Name : People
Primary Key : PersonID
Table Name : Education
Primary Key : EducationID
Tied with People Table via PersonID Field
Table Name : JobStatus
Primary Key : JobStatusID
Tied with People Table via PersonID Field
etc, etc, etc
it will make it a lot eaiser in the long run for scalability when adding even more
fields to databases as well as multiple records over time, what if the person has 2
degrees from different institutions? Or what if you want to keep track of that
persons Job history? Multiple records in a seperate table will be much eaiser to
track and query than running into comma delimited fields in one column of a table....
just my .02
kevin
---------- Original Message ----------------------------------
From: "Jason Lotz" <[EMAIL PROTECTED]>
Reply-To: [EMAIL PROTECTED]
Date: Tue, 20 Mar 2001 09:52:01 -0700
>This is more of a theory question than an actualy request for help. Let's
>say you are building a database of members with lots of information that
>applies to every member (name, address, phone, etc.) This could be about 40
>seperate fields. Then, on top of that, each member can have lots of
>optional information that can easily be grouped together. For example, if
>they graduated from college, you want to store their degree information or
>if they own a company, you want to store their company info. Each of these
>"optional groups" are one-to-one (each member can only have one chunk of
>this data but doesn't have to have it at all.) Now here's the question -
>
>When you are building this database, you could easily put it into one huge
>table because all the information is one-to-one. However, it's a pain when
>you only want to get the "degree" information or the "company" information.
>>From a programming standpoint, is it best to break these into smaller tables
>for ease of use or to keep it into one table?
>
>Thanks,
>Jason
>
>
>
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
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
