Turning a specialisation into tables

• A

  One employee table with both extra columns, nullable, plus a type column

• B

  Three tables: employee, teacher and admin, joined when needed

• C

  Two tables, teacher and admin, with the employee columns duplicated in each

• D

  One table per employee type, created dynamically as new types appear