I have what i think is the correct normalization of my Restaurant DB. I have reworked it into 3 tables currently.
The issue that has given me problems and i am still a bit worried about is Restaurant type. The issue is if a Restaurant served say Italion and Chinese. ie 2 RestType's
Note: this will be with mySQL and PHP
Table 1 : Restaurant
RestID|RName|RStreet|CityStateID|RZip|RPhone#|ROpe
n|RClose|RMenu|RDelivery?|RRating|
Table 2: City and State
RCityState|City|State|
Table 3: Restaurant Type
TypeID|RestID|RestType|
The questions i have are
A) is Table 1 too big. Its not like i am building a monster Dbase of all Restaurants in America but it seems rather large. In your experiance would you reduce this table just for size purposes.
😎 The Restaurant Type. Again if a Restaurant has 2 types ie. Chinese and Italion is this the way to handle it. The RestID allows for a connection between the two tables.
C) Joins the area with the most overhead (i think) joining any or all of these tables keeps it small and doesnt look like too much of an issue. I guess thats the positive of the size of Table 1.
and finally
D) Has this been reduced all the way down to its core. Normalization is a bit of a "Too little or Too much is a bad thing" and so any further reduction would just be useless.
Any thoughts and experiance sugestions would really be apprecated thank you
