Instead of using inheritance, you should use a role based solution. One of the cleanest I've used is Acl9, http://github.com/be9/acl9/tree/master
This will also fit your needs for future complexity since roles are abstracted out of the model and into a separate table. So if you ever need to add more roles, it wouldn't change your database design at all. On Apr 11, 2:27 am, Tam Kbe <rails-mailing-l...@andreas-s.net> wrote: > Hello, > > I have a design question concerning my app with Rails. I have two types > of users let's call them Type1 and Type2. They both have very similar > attributes but different associations and functionality. > > So for every type of user I will need different "has_many, > has_one,...etc" > > Is it better to create one model and have another column called "type" > knowing that whenever the model is loaded the associations for bother > types will be loaded or is it better to create two separate models and > have every model gets its own associations? > > I care about performance but if it's not significant then it doesn't > matter as much. I also care about complexity in case the application > expands in future. > > Thanks, > > Tam > -- > Posted viahttp://www.ruby-forum.com/. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group. To post to this group, send email to rubyonrails-talk@googlegroups.com To unsubscribe from this group, send email to rubyonrails-talk+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/rubyonrails-talk?hl=en -~----------~----~----~----~------~----~------~--~---