Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
Just a simple question, say I have a table and one of their attributes is jobs… the job options can be from 0-20 characters (varchar(20))… is this okay or should I create a mapping table so that a = job1, b = job2, ..etc..etc, so when I insert to the database, I insert it as an ‘a’ instead of job 1.
Yes, but I would let the Jobs lookup table use an integer as the primary key instead of a, b, c, etc.
This way you can give the users a combo box or a list box to enter this value (They see the long name and not the number/key).
Also, from an administrative perspective you can let someone just enter more Jobs in the Jobs table and they will be available without any special coding.
You will have to join these tables anytime you want to link the full job description.