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 each table by a
>college_ID, that's unique and assigned to each college, and maintained in a
>master_collegeTBL...
>
>thoughts/comments/etc....
>
>i'm leaning towards the side that keeps each college information separate,
>although this means that i essentially have to deal with 1000s of
>tables/files...
>
>-bruce
>[EMAIL PROTECTED]
>
>  
>
You're *far* better off putting everything in one table and using a
field in the table, for example CollegeID, to identify which column
you're dealing with.

-- 
Daniel Kasak
IT Developer
NUS Consulting Group
Level 5, 77 Pacific Highway
North Sydney, NSW, Australia 2060
T: (+61) 2 9922-7676 / F: (+61) 2 9922 7989
email: [EMAIL PROTECTED]
website: http://www.nusconsulting.com.au

-- 
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe:    http://lists.mysql.com/[EMAIL PROTECTED]

Reply via email to