Best Practice for Model Design in Ruby on Rails -
the ror tutorials posit 1 model per table orm work. db schema has 70 tables divided conceptually 5 groups of functionality (eg, given table lives in 1 , 1 functional group, , relations between tables of different groups minimised.) so: should design model per conceptual group, or should have 70 rails models , leave grouping 'conceptual'? thanks!
i cover in 1 of large apps making sure tables/models conceptually grouped name (with 1:1 table-model relationship). example:
events event_types event_groups event_attendees etc...
that way when i'm using textmate or whatever, model files nicely grouped alpha sort. have 80 models in app, , works enough keep things organised.
Comments
Post a Comment