I've used restful_authentication and role_requirement for a similar situation. It's easy to setup, and should allow you to do all the stuff you want. As far as the associations you speak of, you probably to setup some different find methods with_scope. Check out the following links for more info...
http://github.com/timcharper/role_requirement http://github.com/technoweenie/restful-authentication http://api.rubyonrails.org/classes/ActiveRecord/Base.html#M002256 On Feb 20, 1:02 am, Mrkris Mrkris <[email protected]> wrote: > Ok, this is a tricky situation. I have a user system where a user might > be an admin, a director, an actor/actress, an extra, or a member At > first, STI sounded great, mainly because a member could just browse, a > directory and actor/actress has_many movies, and so on. Then I realized > that a director could also star in a movie, so, STI wouldn't work > because of the overlap. > > I'm not sure what to do to build this cleanly, I mean, it'd be easy to > use STI so I can have model relationships based on type, but if you > can't share the models, what am I to do? Use a hacky implementation of > roles? > > Thoughts? Suggestions? > > Thanks! > -- > 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 [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/rubyonrails-talk?hl=en -~----------~----~----~----~------~----~------~--~---
