I've got user and artist. The app allows users to register. And some of these registered users can sign up as an artist as well.
Should user be an STI? Perhaps i can have user as an STI, member (registered users) and artist models that inherit from user? My concern is, if we go ahead with the STI approach. Consider this scenario. A user registers. The record is saved and type=user. Later on the same user signs up as an artist. How would we change the type for this user? Should this be done in the Artist controller, create method? i.e. a look up will be performed, and if user found (user.type = 'Artist'; user.save!) Or should user and artist be separate tables on their own? i.e. user has_one :artist, artist belongs_to :user? Any other better approach? -- 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.
