I am working on a project where there are several types of users (students and teachers). Currently to store the user's information, two tables are used. The
I think this design is fine, assuming that most of the time you only need the
user data, and that you know when you need to show the
In addition, you get only teachers just by doing a
JOIN, which might come in handy.
Tomorrow you might have another kind of user who is not a teacher, and you'll be glad of the separation.
Edited to add: yes, this is an inheritance pattern, but since he didn't say what language he was using I didn't want to muddy the waters...