Proper Database Format
I'm trying to store hotel data with all of it's amenities. What is the proper way of creating such a database.
Should I have a hotel table with 50-100 fields or create a relational table that stores amenities and join them later.
I can see how the relational table would save storage on hotels with no amenities but you're losing processing time by searching and joining the table.
Not sure the best way to go about this issue.
Any help would be appreciated.
Anybody have any ideas on the design for this?
Users Browsing this Thread
There are currently 1 users browsing this thread. (0 members and 1 guests)