How do I correctly model data in SQL-based databases that have some columns in common, but also have
- by Brandon Weiss
For instance, let's say I have a User model. Users have things like logins, passwords, e-mail addresses, avatars, etc. But there are two types of Users that will be using this site, let's say Parents and Businesses. I need to store some different information for the Parents (e.g. childrens' names, domestic partner, salaries, etc.) than for the Businesses (e.g. industry, number of employees, etc.), but also some of it is the same, like logins and passwords.
How do I correctly structure this in a SQL-based database? Thanks!