Hi there Rudy and Guido,
have you had a moment to look at my previous post? Could you please advise if this is an appropriate way of designing the amenities tables, or do I need to change anything?
@cydewaze - thanks for your input.
Thank you very much!
so I would have 3 tables for the amenities:
amenities_id amenity_name amenity_type
1 spa feature
2 nature walks feature
3 daily cleaning service
4 free SQL lessons service
5 large pool feature
hotel_id amenities_id type value
1 5 indoor heated
If the above is how the tables should be structured, I would still need another id in the hotel_amenities_info table to relate to the hotel_amenities table – right? If I wanted to, could I add another type-value pair for the same hotel amenity? Using the large pool as an example, I'd have "indoor heated" followed by a new row with a new type-value pair: "size 30m".