Petr Bobek wrote: > I was planning to create subdomain for each author, so I want to > seperate them from the normal users. > > > > Maurício Linhares wrote: >> Why does it need to be a type? What makes an author so different to >> make it different from a common user?
You could use a type column, and single table inheritance, but I suggest creating a separate Author model with its own authors table, and have a user_id in that table. This way, an Author belongs_to a User. All author-specific data goes in the authors table, and you can reuse all of your authentication with the User model. Alternatively, users could have an author_id, if that makes more sense. -- Posted via http://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 -~----------~----~----~----~------~----~------~--~---
