EdwardPeter
asked on
Citizenship table design
Hi,
Please kindly assist how do we design a citizenship table?
User will input his name and choose 1 citizenship
-American
-Canadian
-Others (specify why)
when user selects Others he/she need to input on why they choose that option (remarks).
CustomerTable
CustomerID
CitizenID
CitizenTable
CitizenID
CitizenShip
How will we design the remarks table to link to CitizenTable? Not sure if we need to link to Citizen or we can link it straight to Customer table.
Thanks.
Please kindly assist how do we design a citizenship table?
User will input his name and choose 1 citizenship
-American
-Canadian
-Others (specify why)
when user selects Others he/she need to input on why they choose that option (remarks).
CustomerTable
CustomerID
CitizenID
CitizenTable
CitizenID
CitizenShip
How will we design the remarks table to link to CitizenTable? Not sure if we need to link to Citizen or we can link it straight to Customer table.
Thanks.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
I can't think of any disadvantage of having a nullable column in your CustomerTable. It's not going to take up space if the Citizenship is either American or Canadian.
ASKER
Is there a disadvantage if we added a nullable column vs a new table?
Thanks.