Chris W. Parker wrote:
The phone number table is probably a little less important since there isn't much data to be stored, but if you for some reason wanted to add another phone number (pager, cell phone, etc.) it's a lot easier to just add another row to your phone number table than it is to add another column to your User table. Also keep in mind that not every user is going to have every type of phone number (I don't have a fax number, for instance).interesting you say that because i was going to do this same thing except not as completely as i probably should (which i think is what you are suggesting). what i mean is, my extra table of addresses was going to be merely shipping addresses for the customer and nothing else. but i guess i should change it from being just shipping addresses to include any kind of address relating to the customer?
but what about phone numbers? i'm a bit unsure on that one. in my table
as it is now, i have three: business, home, and fax. in what case would
having a phone (number) table be beneficial?
This is only what I've learned from my experience, though, which is pretty limited. Do any of the uber data modelling DBA guru types out there have any input as to what is easiest/most efficient?
-- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
