Closed xnanodax closed 6 years ago
In the current configuration, the restaurants can only have ONE tag, photo, menu, review. Is that what you wanted? We need to overhaul your db schema. We need to add more join tables so we can have a one to many relationship built.
I would suggest for tags to have a Tags table (includes name of tag) and a Tagging joins table (joins tags to restaurant_id). That way you don't have to store multiple row entries that have the exact same tag name for multiple restaurants. Same can be same for payment option and cuisine.
Looks good!
Database Schema
[x] Contains correct datatypes Example: Restaurant's description. (do you want a string or text?) There are a couple more spots to fix the data type as well.
[x] Contains appropriate constraints/details
[x] Contains bullet points after the table that state which foreign keys will reference to which table, or references to the associations which will be made
[x] Correctly formatted
back_ticked
Comments: