Skip to main content

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

2
  • So if i'm understanding correctly, i'd have one table User with the common machinery and three tables Admin/Teacher/Student with each their own information, and a OneToOne relationship from Admin/Teach/Student to User. Commented Apr 19, 2024 at 1:21
  • 2
    @ancyrweb: Some minor details aside, yes. The four tables will strongly mirror where you find your properties in your classes (a property in User will be found in the user table, etc). This also can enable you to (if you want it) generate a user-unique ID for all your admins/teachers/students, so you don't run into cases where all three tables have overlapping ID values; which will significantly simplify any user-oriented logic that you wish to write that relies on a given ID without needing to guess which table it might be from. Commented Apr 19, 2024 at 4:05