CODEWITHSUNDEEP
mysqldatabase-design
Gonzalo Acosta
Gonzalo Acosta

Reputation: 135

SQL table OR field

I have a conceptual question.

My DB has a table that stores information about people. One of it's fields is their phone number (8-digit for my country).

The thing is that in some cases, two or more people will have the same phone number.

My question is: will it be a better choise to store the phone numbers on another table and then reference it by a foreign key instead of just storing them as a field?If so, will the result be the same for whatever the size of the DB is?

I don't know if this will make any difference, but the table will have no more than 600.000 - 800.000 records, and I guess the coincident phone numbers will be about 10% of the total records.

EDIT:

-Each record can have up to 4 phone numbers (two lines and two cells)

-Both cases will occur, there will be sometimes where the users will be looking for all the people having a specific number, and times where the user will want to know what are all the phone numbers a person has

Upvotes: 1

Views: 57

Answers (4)

Alex
Alex

Reputation: 17289

If you have more then 1 phone number per person

There is a good reason to set new table like: id, user_id, phone, type, description

So type could be list of Home, Work, Office2, Boss, Wife, Fax, Mobile etc...

and description like "work hours only", "evening", "24x7", "Emergency only" etc

If you really manage phone book for your application that is good idea to separate phone numbers from original user table.

Upvotes: 1

MaxZoom
MaxZoom

Reputation: 7753

Usually the phone number is just a number, and without a person has no meaning. So you store it in the Person table.

But it you work for a telephone company for which a phone number has a different meaning and usage (like history, phone lookup, billing) then it should be stored in a separate table. I hope it helped.

Upvotes: 0

HLGEM
HLGEM

Reputation: 96640

Technically to be normalized, you would have a separate Phone number table and then a PersonPhonenumber table.

However, in practice I have rarely seen this structure for phone numbers and addresses. For one, it is easy to make a mistake and update more than one person's addess or phone when you only mean to change one. For another it adds an extra join that seems unnneeded to most people. You aren't really gaining much by going to this level other than a small amount of duplication.

The real decider is how you are going to use and update the numbers. If you want to update all the people with the same number frequently, it is better to go fully normalized. If you will usually only want to update one person at a time, it is probably less risky to only have a Person table and a PersonPhone Number table.

If you want history, then I would go with a person table and aPersonPhoneNumber history table. It would have the personid, the phone number, the startdate and the end date. So when John and Mary get divorced, his phonenumber woudl have an end date but hers woudl not and you could clearly see who had the number when.

Upvotes: 1

Kirk Powell
Kirk Powell

Reputation: 910

If you have two people with the same phone number you will encounter a problem when searching for a specific phone number. A search for a specific phone number will sometimes return more than one result (10% according to your estimate). If you search by phone number AND by people, you can require all searches for a phone number to include a user identifier (first name, last name, location, etc). It depends on what your objective is.

Upvotes: 0

Related Questions