You may want to look into normalization to keep
everything organized. However if you want pure query
speed, you will have to de-normalize some of your
tables to get optimum speed.
Have a look here for info on normalization:
http://databases.about.com/od/specificproducts/a/normalization.htm
HTH
-
bruce wrote:
hi...
i'm considering an app where i'm going to parse a lot of colleges (~1000)
faculty information. would it be better to have all the faculty information
in one large table or would it be better/faster to essentially place each
college in it's own separate table, and reference ea
You have not said what type of information you will be storing in this
database. Is it going to be just faculty information? Even if it is
just faculty information, you do realize that each school treats
departments a bit dfferently. The faculyt maybe under different
school, may specialize in certa
bruce wrote:
>even though this might mean i get a table with 5 million records??? as
>opposed to say a 1000 different tables, each with 50,000 records?
>
>-bruce
>
>
That's right.
Databases are made for this sort of thing.
If you have a separate table for each location, constructing queries to
p
-bruce
-Original Message-
From: Devananda [mailto:[EMAIL PROTECTED]
Sent: Thursday, July 07, 2005 6:07 PM
To: [EMAIL PROTECTED]
Cc: mysql@lists.mysql.com
Subject: Re: database structure question...
I would strongly recommend creating one table, with a column that stores
the colleg
I would strongly recommend creating one table, with a column that stores
the college_ID for each faculty member, and a separate table to
correlate college name and college_id. For example...
Create table faculty (
last_name varchar(50),
first_name varchar(50),
college_id
@lists.mysql.com
Subject: Re: database structure question...
bruce wrote:
>hi...
>
>i'm considering an app where i'm going to parse a lot of colleges (~1000)
>faculty information. would it be better to have all the faculty information
>in one large table or would it be better/faster
bruce wrote:
>hi...
>
>i'm considering an app where i'm going to parse a lot of colleges (~1000)
>faculty information. would it be better to have all the faculty information
>in one large table or would it be better/faster to essentially place each
>college in it's own separate table, and referenc
