For the relational model below, give the corresponding entity-relationship diagram showing the relationships with their degree and participation conditions, the corresponding entity type definitions, and the constraints. An entity type should not be used to represent a relationship. relational model EventPlanner Domains EventCodes ={e0001e9999} VenueCodes ={v01v99} CatererCodes ={ca01ca99} EntertainerCodes ={ en01 ...en99\} Customer Codes ={cu0001cu9999} InvoiceCodes ={00019999} Dates = standard dates Times ={0:0023:59} PeopleCounts ={19999} PriceBands ={ economy, midprice, luxury } EntertainerTypes ={ singer, band, magician , comedian } Names = string relation Event EventCode: EventCodes CustomerCode: CustomerCodes Date: Dates Start Time: Times EndTime: Times NumberOfPeopleExpected: PeopleCounts VenueCode: VenueCodes CatererCode: CatererCodes primary key EventCode foreign key VenueCode references Venue foreign key CatererCode references Caterer relation Venue VenueCode:VenueCodes Capacity: PeopleCounts PriceBand: PriceBands primary key VenueCode constraint ((project Venue over VenueCode) difference (project Event over VenueCode)) is empty relation Caterer CatererCode: CatererCodes MaximumNumberOfPeopleCanCaterFor: PeopleCounts PriceBand: PriceBands primary key CatererCode relation Entertainer EntertainerCode: EntertainerCodes Name:Names EntertainerType: EntertainerTypes primary key Entertainer Code relation EntertainedBy EventCode: EventCodes EntertainerCode: EntertainerCodes primary key (EventCode, EntertainerCode) foreign key EventCode references Event foreign key EntertainerCode references Entertainer relation Invoice Invoice Code: InvoiceCodes EventCode: EventCodes DatePresented: Dates primary key InvoiceCode alternate key EventCode foreign kev EventCode references Event