Hello,

I want to make a database for a website. The visitor of this website can search a hostal in our area and look at the description and photo's.

I have these tables now:
- Table Username: username, password for hostal owner to log in to register or change the data of his hostal
- Table HostalName: HostelID, name hostal, adres, phonenumber, email, name of owner e.g.
- Table Hostal: HostelID, description, photo's, a lot of facilities (about 100 YES/NO-fields in database)
- Table Rooms: HostalID, DescriptionRoom1, PhotoRoom1, FacilitiesRoom1 (about 10 YES/NO-fields), DescriptionRoom2, PhotoRoom2, FacilitiesRoom2 (this can go up to 10 rooms) e.g
- Table Recommandations: HostalID, scores given by visitors that have visited the hostal

My questions:
Is this a logical setup?
Is the table Rooms to big: if a hostal has 10 rooms the amount of colums wil be more then 100. Is this a problem? Is it better to make a table for each room?

Thanx
Rob

It would be best to have a generic table for each Room

Room: RoomID, RoomNumber, HostalID, Description, Photo, Factilities

Not have multiple columns for each room in the Hotel, that what rows are for.

Dont forgot that each table should have a unique numerical id, for the database to
work with.

int RoomID primary key auto_increment

Are your Photos going to be Blobs in the database, or string pointing to files on your server
(i suggest strings)

Username might want to include a user type, in case you have different class of users.

Barry
SQL Programming Feed @ Feed Distiller