Alert the user when using possibly conflicting words as model names

[iox]

Some common errors come from naming models with words that later create conflicts. It would be nice if we introduced some checks in the generators to help users.

Examples:

• Use "page" as model name (reported in https://groups.google.com/forum/#!topic/hobousers/_IDRq45XaTA)
• Use "test" as column name and "number" as column type (https://groups.google.com/forum/#!topic/hobousers/_IDRq45XaTA)
• Create a model adding an extra "s", like hobo g resource events name:string
• Use "request" as model name (https://groups.google.com/forum/#!searchin/hobousers/reserved$20word/hobousers/PcjXcrGhNTk/5HNPDu7HyREJ)
• Use "new/news" as model name (https://groups.google.com/forum/#!searchin/hobousers/reserved$20word)

[haslinger]

I lately fell into

• Use "type" as column name (reserved for STI models)

I was then searching for such a list (in rails context, not hobo specific) and found several:

• http://bparanj.blogspot.co.at/2011/07/reserved-words-in-rails.html.
• Ryan Bigg works on this: https://github.com/radar/rails-reserved-words
• http://reservedwords.herokuapp.com/
• https://github.com/walterdavis/railsready/wiki
• The active record basics guide has some info : http://edgeguides.rubyonrails.org/active_record_basics.html
• another list is over here: http://www.addedbytes.com/cheat-sheets/ruby-on-rails-cheat-sheet/

None of them are authoritative, all of them are outdated, I guess. I think it's a bit of a needle in a haystack task ...

[JezC]

And column name "counter", IIRC. That's also used for something... I ran into this with a Hobo project a couple of years ago. Totally mystified by why I couldn't get the column to show, until I eventually tracked down a mention. I vaguely recall something about counter caches in ActiveRecord.

[iox]

Thanks people, these resources are great :).