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 have a very simple table called genre, which looks like this:
GENRE
=====
id int
genre_category varchar()
genre_category has values like "narrative", "myth", and so on.
genre_category seems like a silly name for the column. The column could be called genre_type or genre_label or genre_category. But it seems redundant.
So, is there any reason not to just go ahead and call it genre.genre?
EDIT:
The bottom line is that it’s better to use .name. Thanks everyone!
It sounds like you’re modeling a genre entity. Examples horror, drama, romance. Is this correct?
Would you be comfortable in calling your
genre‘s column[name]?