You could merge them and just turn off the use of the non-relevant parts, probably easier in the short term but more brittle if you're going to have a lot of user logic (as each method that differs will need to make the check first).
Another possibility would be to keep user as just the core info and have it have associations to 2 models to handle the two cases. Nothing particularly pretty. Maybe Matt or Bryan can suggest something better. -- You received this message because you are subscribed to the Google Groups "Hobo Users" group. To view this discussion on the web visit https://groups.google.com/d/msg/hobousers/-/KjXA3R8vFkQJ. 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.
