Be part of JetBrains PHPverse 2026 on June 9 – a free online event bringing PHP devs worldwide together.
Hey guys! I'm planning to create an application that will have student and professor roles. Since I will have a couple unique fields for students and other unique fields for professors, how would you guys recommend me to organize my tables? Let's say I do not want to have the e-mail and registration number field for professors, but I do want to have those for students. Should I create the users table with all of the fields and leave the e-mail and registration number blank for professors? I know it is possible to create multi-auth authentications and work with two different tables, but I'm avoiding doing that to make things simple
I think this depends on how many unique fields will have, if there are too many then it could get cumbersome having to have them in one table. Maybe one table can have the common fields then two other tables to handle the fields unique to each of the roles. But lets say they are just a few unique fields in each, it may be fine having them in one table and set them as nullable. I'm thinking you may eventually have users, profiles, student_profiles, prof_profiles.
Thank you very much!
Please or to participate in this conversation.