See, that's the thing with having a foreign key relationship. Depending on your business logic, the relationship could be 0-N. So, you could have as few as 0 entries in the 2nd table, or as many as you want. That way, you can treat each entry separately.
I don't know your exact implementation, so let's assume the following case:
You have a user table that stores basic information. You want the ability to store multiple phone numbers for one user, but don't want to limit the amount of numbers. You are suggesting creating a phone field, and put multiple values in that. Rather than doing that, create a separate table, and utilize the primary key from the first table to reference the userID.
Say your user table has the following fields:
userID (primary key)
name
email
address
Your phone table would have something like this:
phoneID (primary key)
userID (foreign key - references user table)
phoneNumber
numberType
Sample data may be as follows:
This way, you can see that phone numbers 1,2, and 3 all belong to userID 1(Steve)
Then, to get all of Steve's phone numbers, you could do the following:
sql Code:
SELECT * FROM phone_table WHERE userID = '1'
This should help - or at least get you started in the right direction. I suggest doing some reading on relational databases and in particular, JOINS (how to select multiple tables at once and "link" together).
Good Luck!