I have pretty much decided to go with a single user model with attributes that determine the type, and other models which refer back to the user model. I guess the question is really academic, therefore, unless someone has some good insights. Thanks.
On Mar 7, 11:38 pm, mydoghasworms <[email protected]> wrote: > Sorry if this is covered somewhere, but I am unable to find something > on it: > > Does Hobo support multiple user models? E.g. I have needs for > different types of users. I'm not sure whether any of the other > solutions, STI or Polymorphic relationships are the answer. In my > case, I need to provide users that place adverts for jobs > (advertisers) and users who are job seekers. They would have widely > varying attributes, and I would see them as completely different > entities, so I would think having separate models would be best. > > However, how does Hobo engage with multiple user models? How does this > affect authentication and permissions? -- You received this message because you are subscribed to the Google Groups "Hobo Users" 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/hobousers?hl=en.
