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.
I’m going to create a table for holding set of options, right now its around 30 different options. But it will gradually increase month by month, if I set a table per field per option basis its going to have 30+ and the worst part I have to modify it whenever I add a new option, The options are are grouped. I was thinking something like this. A separate table to hold a group id of set of options, and for the option another table.
option_id | group_id | option_name | option_value
Thank You.
looks nice, but in my personal opinion, i would change option_id to ID, option_name to Name and option_value to Value.
group_id is good as it is, so you can know that it’s linked to another table, as for the others, it’s completely unnecessary. If the table name is Options, you normally assume that the field Value is the Option Value.
Hope that helped.