Feature Request: Provide documentation and/or feature to configure active record naming conventions

rubyonrails-core
1

So far I’ve just manually used set_table_name and set_primary_key and similar things in models that must access legacy database tables. It’s worked well with camel case for me so far. Scaffolding models can only get you so far, most of the time I don’t even bother with it anymore since it only saves me typing a couple lines anyway.

Dave

2

Same process here. We have a system that uses dozens of tables and views from PeopleSoft. We just use set_table_name and set_primary_key and never use the generators (don’t see much value in them myself).

Cheers,

Anthony

3

You should look into ActiveModel::Naming. You might be able to override certain methods to return a custom subclass of ActiveSupport::Name to do what you want.

YMMV

Godfrey