$2.[36$pts$]$ Assume you are helping design a database for the fictional world for a film studio. This database will include information about basic information of the locations, people,

$-$ Information about Character includes their name, their ID$,$ and their favorite food. Each Character must be either CGI or a Human $($but not both$).$ Each CGI character should have a type $($such as Dragon or Zombie$).$ Each Human should have a hair style.

$-$ Information about Actors includes their employee ID$,$ name, salary, and address. An Actor can play at most one Human Character. An Actor can play multiple CGI Characters. $($For example, an Actor can play $3$ CGI Characters, and $1$ Human$).$ Each CGI character must be associated with some actor, while multiple actors can play the same CGI Character. Each human character must have exactly one associated actor.

$-$ A Credit is an instance where a pair of CGI Character and Actor are associated together, representing the instance of an actor playing a particular CGI character. A credit also stores the role of the credit $($such as "Voice" or "Puppeteer"$).$ Each unique pair of CGI character and Actor can only have one credit. That is$,$ you cannot have the same actor taking credits of a CGI character as different roles.

$-$ A Episode consists of multiple credits. A credit may appear in more than one episode. An episode also contains a set of Human Characters which appear in the episode. A Human character may appear in more than one episode.

$(1)$ Draw an ER diagram of the database you designed fulfill all the requirements above. You should capture all constraints without any text in the diagram, except for covering$/$overlap constraints for class hierarchy $($if necessary$).$

$(2)$ Translate your ER diagram into a relational database schema. Specifically, you should write down the DDL statement to create each table capturing all information and constraints given in the diagram. You can decide data types for different attributes as long as they are reasonable. For foreign key constraints, you do NOT need to specify referential actions $($e$.$g$.,$ ON DELETE, ON UPDATE$).$