Welcome to the Treehouse Community
Want to collaborate on code errors? Have bugs you need feedback on? Looking for an extra set of eyes on your latest project? Get support with fellow developers, designers, and programmers of all backgrounds and skill levels here with the Treehouse Community! While you're at it, check out some resources Treehouse students have shared here.
Looking to learn something new?
Treehouse offers a seven day free trial for new students. Get access to thousands of hours of content and join thousands of Treehouse students and alumni in the community today.Start your free trial
Urooba Urooba3,565 Points
where would the non teaching staff would fit into this as not all employess can be teacher?
Jonathan GrieveTreehouse Moderator 91,252 Points
It's been a while since I looked at this course but I think for the purposes of this example we can assume all staff in the database are teachers! :-)
I think the answer to this question would be "it depends"; more specifically, "it depends on how you, as a database designer, think the best way to 'normalise' the tables in the database is, in accordance with the different sets of data and in what way the data will most likely be queried most often".
Perhaps you make a table for 'other staff', or multiple tables for each type of staff (cleaner, administrator, teaching assistant, etc).
Understanding the different options, weighing them up, and implementing a solution you can explain is what would make you valuable to an organisation! :)