Question: consider the following relational database to manage concert and ticket...
Consider the following relational database to manage concert and ticket sales. The relations are artist, concert, venue, seat, ticket, and fan. The schemas for these relations (with primary key attributes underlined) are:
Artist-schema = (artistname, type, salary)
Concert-schema = (artistname, date, venuename, artistfees)
Venue-schema = (venuename, address, seating_capacity)
Seat-schema=(venuename, row, seatnumber)
Ticket-schema = (fanID, date, venuename, row, seatnumber)
Fan-schema = (fanID, name, address, creditcardno)
• artistname is a unique name for the artist (because of trademark/copyright rules no two artists have the same name).
• type is an attribute whose value is chosen from “music”, “comedy”, “juggling”, or “other”
• artistfees is a real number greater than 0
• fanID is a unique ID given to a customer
• creditcardno is a 16 digit credit card number starting with a 4 or a 5. a)
1 Draw a schema diagram for this database. Be sure to indicate all foreign keys implied by the attribute names and primary keys in the relation schemas.
2) Does this database schema allow for one fan to have multiple tickets for a given concert? Justify.
3) Does this database schema allow for multiple artists to play a given venue on a particular date? Justify.
4) Could the date attribute in ticket be a foreign key referencing only the date attribute in concert? Justify.
5) Why would a foreign key in ticket referencing venue NOT provide any additional constraints?