foo.foo: Is giving a table column the same name as the table itself a bad idea?

Viewed 5204

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!

3 Answers
Related