Although you always wanted to be an artist, you ended up being an expert on databases because you love to cook data and you somehow confused database with database. Your old love is still there, however, so you set up a database company, ArtBase that builds a product for art galleries.
The core of this product is a database with a schema that captures all the information that galleries need to maintain.
- Galleries keep information about artists, their names (which are unique), birthplaces, age, and style of art.
- For each piece of artwork, the artist, the year it was made, its unique title, its type of art (e.g., painting, lithograph, sculpture, photograph), and its price must be stored. Each piece of artwork is known to be painted by only one artist.
- Pieces of artwork are also classified into groups of various kinds, for example, portraits, still lifes, works by Picasso, or works of the 19th century; a given piece may belong to more than one group. Each group is identified by a name (like those just given) that describes the group.
- Finally, galleries keep information about customers. For each customer, galleries keep that person’s unique name, address, total amount of dollars spent in the gallery (very important!), and the artists and groups of art that the customer tends to like.
Draw the ER diagram for the database. Please make sure to specify all entity sets with their attributes and keys, and all relationship sets with relevant key constraints and/or participation constraints.
Solution:
