Hope this question is right here.TL;DRDatabase design for event places (venue and hotel), hotels can be venues.Long VersionIntroductionI'm developing a software for trainings. Trainings are like a template with information and events show time and place where a specific training will happen.Events have a place where they happen, the venue. Events also have an (optional) hotel, where participants can book rooms. A hotel can also be a venue since they often have conference rooms.So if a hotel is  venue all the contact information and address for the hotel and the venue are obviously the same.QuestionWhat is the best way to design the database for hotel and venue, so that a hotel can also be a venue.Target of design:avoid duplicate data if a hotel is a venueeasy to handle through my softwarePossible solutionsone table Place with columns hotel_ID and venue_ID which link tothe tables Hotel and Venueone table place with an isHotel and isVenue column indicating which it istwo separate tables hotel and venue and in hotel table a column venueID whch links to a venue?... (something different)
Event places - venue and hotel (database design conceptual question)
database design