SQL language A movie may have many actors, and an actor can act in many movies. A movie may have many animators working on it, and an animator may work on many different movies. Suppose we try to represent this in our database using a single "Credits" table, with columns movie_id, actor_id and animator_id. The key of the table is the combination of all 3 attributes. The attributes are each foreign keys to tables for Movies, Actors and Animators, respectively. What is wrong with this? The table would be too big Either the actor_id or animator_id field would be null An actor may play more than one role in the same movie Not all movies have actors.