# Do I pile up mutiple cruds in one controller?

**URL:** <https://www.ruby-forum.com/t/do-i-pile-up-mutiple-cruds-in-one-controller/120354>\
**Category:** Rails\
**Created:** [November 16, 2007, 4:15am UTC](https://www.ruby-forum.com/t/do-i-pile-up-mutiple-cruds-in-one-controller/120354 "2007-11-16T04:15:09Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![tomn](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/t/c89c15/32.png) [@tomn](https://www.ruby-forum.com/u/tomn)\
**Post date:** [November 16, 2007, 4:15am UTC](https://www.ruby-forum.com/t/do-i-pile-up-mutiple-cruds-in-one-controller/120354/1 "2007-11-16T04:15:09Z")

</div>

Being so new to programming, I really don’t have a clue to the proper  
convention to use.

I have a schema where users will be storing personal data in a number of  
different models, some of them dependent on others and all linked to at  
least one, usually two or three others models via foreign key or habt  
jointable.

I don’t want other users to access each others data… so no instances  
of any model except for user will exist without foreign keys.(well there  
will be joint tables) There will be little reason to use the base crud  
stuff a scaffold would make for each model…maybe for the deletes?

Most of the views too will all be from the user controllers I think…  
they all will have multiple models involved.

Do I just make a really long user controller with the 3 or 4 crud  
actions for each model i use? create\_model1, create\_model2,  
create\_model3, create\_model4 …and the same for edit updates delete  
etc?

The redundancy is a shame in itself but as they all have a bit different  
types of relations with other models its gotta be there.

To make this question short and sweet (lol), if you have a dozen models  
that interact at few focused view pages is it normal to have a  
controller a dozen pages long?