Jake, I couldn't help but feel sorry for you in the path you're taking. Simply create a has_one and belongs_to relationship between a controlling master record such as Student_Type(Teacher, Student, etc). Now, when you call a record its @student_type.users(find ??). That inheritence stuff is for the race car drivers and opens up many potholes that could CRASH your effort. Hope this makes your life a little easier. David
On Oct 24, 12:56 pm, Jake Boxer <jacob.bo...@gmail.com> wrote: > After a lot of careful research, I've made the decision to go with > Authlogic (http://github.com/binarylogic/authlogic) for > authentication in my app. > > I currently have a User model (which "acts_as_authentic" in > Authlogic). However, my app is going to have multiple user types > ("Teacher", "Student", and potentially "Teacher's Assistant"). For the > moment, they'll all be mutually exclusive; a user can't be both a > Teacher's Assistant and a Student, for example. > > Currently, I'm planning on creating separate models for each of these > (Teacher, Student, TA). They'll each "belongs_to" a User, and a user > will "has_one" of each. This way, I'll be able to put any common > methods/fields in User, and any exclusive methods/fields in the model > it belongs in. > > I'm very new to Ruby (and, by association, to Rails). Does this sound > like a reasonable way to do this? Does it follow "the Ruby/Rails way"? > Or is there a common pattern for doing this in Rails that I don't know > about? > > Thank you very much in advance > -Jake --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
