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 see some people design design their database having a column STATUS INT where they add values like 0- not active, 1-active, 2-pending . What is the difference between just making an enum(‘not active’,’active’,’pending’). Is it a better database design to not have strings defined for fields and use integers?
If option are limited and fix use enum with direct
('not active','active','pending')Otherwise it will be better to make child table for options and store corresponding integer id(
Primary keyof child table) in parent table.