现在多选择99分酒，两人都觉得小四哥。作为蓝带主厨，他出品清新而有张力的烧腊，不管是他特别推的叉烧、被誉为世界最好的片皮鸭、水晶虾饺皇还是豉油鸡都不会过咸油腻，也没有一般港式茶餐厅的重口味。虽然不是正统粤菜，但他们家师傅的手艺相信得到广东师傅认证了。 内里空间很大，极有气派和格调，适合请客和一家大小来享用，都不算夸张。 Past customers' reviews: 1. "The BBQ pork is the best I've ever tasted!" 2. "Loved their Peking duck, it was perfectly crispy." 3. "Excellent service and elegant ambiance." 4. "Their shrimp dumplings are a must-try." 5. "Authentic flavors and generous portions." Entertainment Suggestion: The waiters sometimes host live music performances on select evenings. To design an SQL data model that supports a detailed review system for restaurants, including entertainment suggestions and detailed customer feedback, we'll need to consider entities such as Restaurants, Reviews, EntertainmentSuggestions, and perhaps Customers if you want to track individual reviewers beyond just storing ratings and comments. Let's build this step by step based on your requirements: ### 1. **Entities and Attributes** #### Restaurants - restaurant_id (PK) - name - address - description #### Reviews - review_id (PK) - restaurant_id (FK) - customer_name (for simplicity, string; for more detail, a Customers table could be added) - rating (e.g., out of 5 or 10) - comment - review_date #### EntertainmentSuggestions - suggestion_id (PK) - restaurant_id (FK) - suggestion_text - applicable_days (optional, e.g., which days events happen) Optionally: #### Customers (if needed) - customer_id (PK) - name - contact_info If you want to associate reviews with registered users/customers, add `customer_id` to Reviews. --- ### 2. **SQL Data Model (CREATE TABLE Statements)** ```sql -- Restaurant Table CREATE TABLE Restaurant ( restaurant_id INT PRIMARY KEY AUTO_INCREMENT, name VARCHAR(255) NOT NULL, address VARCHAR(255), description TEXT ); -- Reviews Table CREATE TABLE Review ( review_id INT PRIMARY KEY AUTO_INCREMENT, restaurant_id INT NOT NULL, customer_name VARCHAR(100), -- or customer_id INT if using Customers table rating DECIMAL(2,1) NOT NULL, -- example: 4.5 comment TEXT, review_date DATE DEFAULT CURRENT_DATE, FOREIGN KEY (restaurant_id) REFERENCES Restaurant(restaurant_id) ); -- Entertainment Suggestions Table CREATE TABLE EntertainmentSuggestion ( suggestion_id INT PRIMARY KEY AUTO_INCREMENT, restaurant_id INT NOT NULL, suggestion_text TEXT NOT NULL, applicable_days VARCHAR(50), -- e.g., 'Fridays, Saturdays' FOREIGN KEY (restaurant_id) REFERENCES Restaurant(restaurant_id) ); -- Optional: Customer Table CREATE TABLE Customer ( customer_id INT PRIMARY KEY AUTO_INCREMENT, name VARCHAR(100) NOT NULL, contact_info VARCHAR(255) ); ``` --- ### 3. **Sample Insert Statement Example** ```sql INSERT INTO Restaurant (name, address, description) VALUES ('Little Four Bro', '123 Main St.', 'Famous for its light yet flavorful barbecue and elegant ambiance.'); INSERT INTO Review (restaurant_id, customer_name, rating, comment) VALUES (1, 'Alice', 5, 'The BBQ pork is the best I\'ve ever tasted!'), (1, 'Bob', 5, 'Loved their Peking duck, it was perfectly crispy.'), (1, 'Charlie', 5, 'Excellent service and elegant ambiance.'), (1, 'Diana', 5, 'Their shrimp dumplings are a must-try.'), (1, 'Edward', 5, 'Authentic flavors and generous portions.'); INSERT INTO EntertainmentSuggestion (restaurant_id, suggestion_text, applicable_days) VALUES (1, 'Waiters sometimes host live music performances on select evenings.', 'Fridays'); ``` --- ### 4. **How to Query** **Get all reviews and entertainment of a restaurant** ```sql SELECT r.name AS Restaurant, rv.rating, rv.comment, es.suggestion_text FROM Restaurant r LEFT JOIN Review rv ON r.restaurant_id = rv.restaurant_id LEFT JOIN EntertainmentSuggestion es ON r.restaurant_id = es.restaurant_id WHERE r.name = 'Little Four Bro'; ``` --- This schema provides: - Multiple detailed reviews per restaurant. - Entertainment suggestions per restaurant. - Optionally tracks named customers. - Extensible for more features like menus, images, etc. Let me know if you'd like any modifications or further details! Here is a robust SQL data model supporting detailed restaurant reviews, customer comments, and associated entertainment suggestions. This model allows multiple reviews per restaurant, stores reviewer names/ratings/comments, and attaches multiple entertainment entries to each restaurant. --- ### **Schema** #### 1. **Restaurant Table** Stores the basic info about each restaurant. ```sql CREATE TABLE Restaurant ( restaurant_id INT PRIMARY KEY AUTO_INCREMENT, name VARCHAR(255) NOT NULL, address VARCHAR(255), description TEXT ); ``` #### 2. **Review Table** Each record is a customer review for a particular restaurant. ```sql CREATE TABLE Review ( review_id INT PRIMARY KEY AUTO_INCREMENT, restaurant_id INT NOT NULL, customer_name VARCHAR(100), -- Optionally link to a Customer table if desired rating DECIMAL(2,1) NOT NULL, -- e.g. 4.5 comment TEXT, review_date DATE DEFAULT CURRENT_DATE, FOREIGN KEY (restaurant_id) REFERENCES Restaurant(restaurant_id) ); ``` #### 3. **EntertainmentSuggestion Table** Holds entertainment suggestions/specials for each restaurant. ```sql CREATE TABLE EntertainmentSuggestion ( suggestion_id INT PRIMARY KEY AUTO_INCREMENT, restaurant_id INT NOT NULL, suggestion_text TEXT NOT NULL, applicable_days VARCHAR(100), -- e.g. "Every Friday" FOREIGN KEY (restaurant_id) REFERENCES Restaurant(restaurant_id) ); ``` --- ### **Sample Inserts** ```sql -- Add restaurant INSERT INTO Restaurant (name, address, description) VALUES ('Little Four Bro', '123 Main St.', '清新而有张力的烧腊，环境优雅，非常适合聚餐'); -- Add reviews INSERT INTO Review (restaurant_id, customer_name, rating, comment) VALUES (1, 'Alice', 5, 'The BBQ pork is the best I\'ve ever tasted!'), (1, 'Bob', 5, 'Loved their Peking duck, it was perfectly crispy.'), (1, 'Charlie', 5, 'Excellent service and elegant ambiance.'), (1, 'Diana', 5, 'Their shrimp dumplings are a must-try.'), (1, 'Edward', 5, 'Authentic flavors and generous portions.'); -- Add entertainment suggestion INSERT INTO EntertainmentSuggestion (restaurant_id, suggestion_text, applicable_days) VALUES (1, 'Waiters sometimes host live music performances on select evenings.', 'Fridays & Saturdays'); ``` --- ### **Example Query** Fetch all reviews and any entertainment suggestions for "Little Four Bro": ```sql SELECT r.name AS restaurant, rv.customer_name, rv.rating, rv.comment, es.suggestion_text, es.applicable_days FROM Restaurant r LEFT JOIN Review rv ON r.restaurant_id = rv.restaurant_id LEFT JOIN EntertainmentSuggestion es ON r.restaurant_id = es.restaurant_id WHERE r.name = 'Little Four Bro'; ``` --- ### **Notes** - You can easily expand this model—for example, add a `Customer` table and link `review.customer_name` to a customer’s id. - The model accommodates as many reviews/comments per restaurant as you wish. - Entertainment suggestions are decoupled and allow for multiple entries per restaurant. This structure should serve your needs for managing multi-review, comment-enabled restaurant information, along with supporting entertainment suggestions. Let me know if you want customization for additional features! Yes, here is a normalized SQL data model that supports multiple reviews per restaurant, each with reviewer name, rating, and comment, and supports associating multiple entertainment suggestions to each restaurant. ```sql -- Restaurant information CREATE TABLE Restaurant ( restaurant_id INT PRIMARY KEY AUTO_INCREMENT, name VARCHAR(255) NOT NULL, address VARCHAR(255), description TEXT ); -- Reviews: Each by a reviewer for a restaurant CREATE TABLE Review ( review_id INT PRIMARY KEY AUTO_INCREMENT, restaurant_id INT NOT NULL, reviewer_name VARCHAR(100) NOT NULL, rating TINYINT NOT NULL, -- e.g., 1-5 or 1-10 scale comment TEXT, review_date DATETIME DEFAULT NOW(), FOREIGN KEY (restaurant_id) REFERENCES Restaurant(restaurant_id) ); -- Entertainment suggestions for each restaurant CREATE TABLE EntertainmentSuggestion ( suggestion_id INT PRIMARY KEY AUTO_INCREMENT, restaurant_id INT NOT NULL, suggestion_text TEXT NOT NULL, applicable_days VARCHAR(50), -- e.g. 'Fridays', 'Weekends' FOREIGN KEY (restaurant_id) REFERENCES Restaurant(restaurant_id) ); ``` ### Example inserts ```sql INSERT INTO Restaurant (name, address, description) VALUES ('Little Four Bro', '123 Main St.', 'Famous Cantonese grill known for clean flavors and great ambiance.'); INSERT INTO Review (restaurant_id, reviewer_name, rating, comment) VALUES (1, 'Alice', 5, 'The BBQ pork is the best I\'ve ever tasted!'), (1, 'Bob', 5, 'Loved their Peking duck, it was perfectly crispy.'), (1, 'Carol', 5, 'Excellent service and elegant ambiance.'), (1, 'Dave', 5, 'Their shrimp dumplings are a must-try.'), (1, 'Eve', 5, 'Authentic flavors and generous portions.'); INSERT INTO EntertainmentSuggestion (restaurant_id, suggestion_text, applicable_days) VALUES (1, 'Waiters sometimes host live music performances on select evenings.', 'Fridays, Saturdays'); ``` ### Example query To list reviews and entertainment for "Little Four Bro": ```sql SELECT r.name, rv.reviewer_name, rv.rating, rv.comment, es.suggestion_text, es.applicable_days FROM Restaurant r LEFT JOIN Review rv ON r.restaurant_id = rv.restaurant_id LEFT JOIN EntertainmentSuggestion es ON r.restaurant_id = es.restaurant_id WHERE r.name = 'Little Four Bro' ORDER BY rv.review_date; ``` This model supports: - Multiple reviews per restaurant (detailed reviewer/rating/comment) - Multiple entertainment suggestions per restaurant - Easy extensibility (e.g. for menu items, photos, etc.) Below is a sample SQL data model to support multiple reviews per restaurant, a reviewer name and comment, and multiple entertainment suggestions: ```sql -- Restaurant master CREATE TABLE Restaurant ( restaurant_id INT PRIMARY KEY AUTO_INCREMENT, name VARCHAR(255) NOT NULL, address VARCHAR(255), description TEXT ); -- Customer reviews CREATE TABLE Review ( review_id INT PRIMARY KEY AUTO_INCREMENT, restaurant_id INT NOT NULL, reviewer_name VARCHAR(100) NOT NULL, rating DECIMAL(2,1) NOT NULL, comment TEXT, review_date DATE DEFAULT CURRENT_DATE, FOREIGN KEY (restaurant_id) REFERENCES Restaurant(restaurant_id) ); -- Entertainment Suggestions CREATE TABLE EntertainmentSuggestion ( suggestion_id INT PRIMARY KEY AUTO_INCREMENT, restaurant_id INT NOT NULL, suggestion_text TEXT NOT NULL, applicable_days VARCHAR(50), FOREIGN KEY (restaurant_id) REFERENCES Restaurant(restaurant_id) ); -- Example insertions INSERT INTO Restaurant (name, address, description) VALUES ('Little Four Bro', '123 Main St.', '清新而有张力的烧腊，环境优雅，非常适合聚餐'); INSERT INTO Review (restaurant_id, reviewer_name, rating, comment) VALUES (1, 'Alice', 5, 'The BBQ pork is the best I\'ve ever tasted!'), (1, 'Bob', 5, 'Loved their Peking duck, it was perfectly crispy.'), (1, 'Charlie', 5, 'Excellent service and elegant ambiance.'), (1, 'Diana', 5, 'Their shrimp dumplings are a must-try.'), (1, 'Edward', 5, 'Authentic flavors and generous portions.'); INSERT INTO EntertainmentSuggestion (restaurant_id, suggestion_text, applicable_days) VALUES (1, 'Waiters sometimes host live music performances on select evenings.', 'Fridays, Saturdays'); ``` This model allows: - Unlimited reviews per restaurant, each with name, rating, comment. - Unlimited entertainment suggestions per restaurant. - Querying all related data via joins. Here’s a normalized SQL schema that supports multiple reviews per restaurant (with reviewer name, rating, and comment) and multiple entertainment suggestions per restaurant: ```sql CREATE TABLE Restaurant ( restaurant_id INT PRIMARY KEY AUTO_INCREMENT, name VARCHAR(255) NOT NULL, address VARCHAR(255), description TEXT ); CREATE TABLE Review ( review_id INT PRIMARY KEY AUTO_INCREMENT, restaurant_id INT NOT NULL, reviewer_name VARCHAR(100) NOT NULL, rating TINYINT NOT NULL, comment TEXT, review_date DATE DEFAULT CURRENT_DATE, FOREIGN KEY (restaurant_id) REFERENCES Restaurant(restaurant_id) ); CREATE TABLE EntertainmentSuggestion ( suggestion_id INT PRIMARY KEY AUTO_INCREMENT, restaurant_id INT NOT NULL, suggestion_text TEXT NOT NULL, applicable_days VARCHAR(50), FOREIGN KEY (restaurant_id) REFERENCES Restaurant(restaurant_id) ); ``` **Example data insertion:** ```sql INSERT INTO Restaurant (name, address, description) VALUES ('Little Four Bro', '123 Main St.', '清新而有张力的烧腊，环境优雅，非常适合聚餐'); INSERT INTO Review (restaurant_id, reviewer_name, rating, comment) VALUES (1, 'Alice', 5, 'The BBQ pork is the best I\'ve ever tasted!'), (1, 'Bob', 5, 'Loved their Peking duck, it was perfectly crispy.'), (1, 'Charlie', 5, 'Excellent service and elegant ambiance.'), (1, 'Diana', 5, 'Their shrimp dumplings are a must-try.'), (1, 'Edward', 5, 'Authentic flavors and generous portions.'); INSERT INTO EntertainmentSuggestion (restaurant_id, suggestion_text, applicable_days) VALUES (1, 'Waiters sometimes host live music performances on select evenings.', 'Fridays, Saturdays'); ``` This model lets you retrieve all reviews and entertainment suggestions for a restaurant and is easy to extend. Let me know if you want to add user accounts or other entities! Here’s a simple, normalized SQL schema for your use case: ```sql CREATE TABLE Restaurant ( restaurant_id INT PRIMARY KEY AUTO_INCREMENT, name VARCHAR(100), address VARCHAR(200), description TEXT ); CREATE TABLE Review ( review_id INT PRIMARY KEY AUTO_INCREMENT, restaurant_id INT, reviewer_name VARCHAR(100), rating DECIMAL(2,1), comment TEXT, review_time DATETIME DEFAULT CURRENT_TIMESTAMP, FOREIGN KEY (restaurant_id) REFERENCES Restaurant(restaurant_id) ); CREATE TABLE EntertainmentSuggestion ( suggestion_id INT PRIMARY KEY AUTO_INCREMENT, restaurant_id INT, suggestion_text TEXT, applicable_days VARCHAR(50), FOREIGN KEY (restaurant_id) REFERENCES Restaurant(restaurant_id) ); ``` **Usage notes:** - Each restaurant can have many reviews (with reviewer name, rating, and comment). - Each restaurant can have multiple entertainment suggestions. **Sample insert:** ```sql INSERT INTO Restaurant (name, address, description) VALUES ('Little Four Bro', '123 Main St.', '清新烧腊，环境优雅，适合聚餐'); INSERT INTO Review (restaurant_id, reviewer_name, rating, comment) VALUES (1, 'Alice', 5, 'The BBQ pork is the best I\'ve ever tasted!'), (1, 'Bob', 5, 'Loved their Peking duck, it was perfectly crispy.'); INSERT INTO EntertainmentSuggestion (restaurant_id, suggestion_text, applicable_days) VALUES (1, 'Waiters sometimes host live music performances.', 'Fridays, Saturdays'); ``` This model supports multiple reviews and entertainment suggestions per restaurant. If you want to track registered users or add more features, let me know! Below is a flexible SQL data model for your scenario: ```sql CREATE TABLE Restaurant ( restaurant_id INT PRIMARY KEY AUTO_INCREMENT, name VARCHAR(255) NOT NULL, address VARCHAR(255), description TEXT ); CREATE TABLE Review ( review_id INT PRIMARY KEY AUTO_INCREMENT, restaurant_id INT NOT NULL, reviewer_name VARCHAR(100), rating DECIMAL(2,1) NOT NULL, comment TEXT, review_date DATE DEFAULT CURRENT_DATE, FOREIGN KEY (restaurant_id) REFERENCES Restaurant(restaurant_id) ); CREATE TABLE EntertainmentSuggestion ( suggestion_id INT PRIMARY KEY AUTO_INCREMENT, restaurant_id INT NOT NULL, suggestion_text TEXT NOT NULL, applicable_days VARCHAR(50), FOREIGN KEY (restaurant_id) REFERENCES Restaurant(restaurant_id) ); ``` This supports: - Multiple reviews per restaurant, each with reviewer name, rating, and comment. - Multiple entertainment suggestions per restaurant. **Example** Insert a restaurant, reviews, and entertainment: ```sql INSERT INTO Restaurant (name, address, description) VALUES ('Little Four Bro', '123 Main St', 'Famous for clean, subtle BBQ flavors—great for gatherings.'); INSERT INTO Review (restaurant_id, reviewer_name, rating, comment) VALUES (1, 'Alice', 5, 'The BBQ pork is the best I\'ve ever tasted!'), (1, 'Bob', 5, 'Loved their Peking duck, it was perfectly crispy.'), (1, 'Charlie', 5, 'Excellent service and elegant ambiance.'), (1, 'Diana', 5, 'Their shrimp dumplings are a must-try.'), (1, 'Edward', 5, 'Authentic flavors and generous portions.'); INSERT INTO EntertainmentSuggestion (restaurant_id, suggestion_text, applicable_days) VALUES (1, 'Waiters sometimes host live music performances on select evenings.', 'Fridays & Saturdays'); ``` Minimal, extensible, and supports your requirements. A relational database schema for your use case: ```sql CREATE TABLE Restaurant ( restaurant_id INT AUTO_INCREMENT PRIMARY KEY, name VARCHAR(200) NOT NULL, address VARCHAR(200), description TEXT ); CREATE TABLE Review ( review_id INT AUTO_INCREMENT PRIMARY KEY, restaurant_id INT NOT NULL, reviewer_name VARCHAR(100) NOT NULL, rating DECIMAL(2,1) NOT NULL, comment TEXT, review_date DATETIME DEFAULT CURRENT_TIMESTAMP, FOREIGN KEY(restaurant_id) REFERENCES Restaurant(restaurant_id) ); CREATE TABLE EntertainmentSuggestion ( suggestion_id INT AUTO_INCREMENT PRIMARY KEY, restaurant_id INT NOT NULL, suggestion_text TEXT NOT NULL, applicable_days VARCHAR(50), FOREIGN KEY(restaurant_id) REFERENCES Restaurant(restaurant_id) ); ``` Key points: - Multiple reviews per restaurant, each with reviewer name, rating, and comment. - Multiple entertainment suggestions per restaurant. **Sample data:** ```sql INSERT INTO Restaurant (name, address, description) VALUES ('Little Four Bro', '123 Main St.', '清新而有张力的烧腊，环境优雅，非常适合聚餐'); INSERT INTO Review (restaurant_id, reviewer_name, rating, comment) VALUES (1, 'Alice', 5, 'The BBQ pork is the best I\'ve ever tasted!'), (1, 'Bob', 5, 'Loved their Peking duck, it was perfectly crispy.'), (1, 'Charlie', 5, 'Excellent service and elegant ambiance.'), (1, 'Diana', 5, 'Their shrimp dumplings are a must-try.'), (1, 'Edward', 5, 'Authentic flavors and generous portions.'); INSERT INTO EntertainmentSuggestion (restaurant_id, suggestion_text, applicable_days) VALUES (1, 'Waiters sometimes host live music performances on select evenings.', 'Fridays, Saturdays'); ``` This schema is efficient, flexible, and supports your requirements for reviews and entertainment suggestions. Here's a well-normalized SQL data model for restaurants, reviews, and entertainment suggestions: ```sql CREATE TABLE Restaurant ( restaurant_id INT PRIMARY KEY AUTO_INCREMENT, name VARCHAR(100) NOT NULL, address VARCHAR(200), description TEXT ); CREATE TABLE Review ( review_id INT PRIMARY KEY AUTO_INCREMENT, restaurant_id INT NOT NULL, reviewer_name VARCHAR(100), rating TINYINT NOT NULL, -- e.g. scale 1-10 comment TEXT, review_date DATE DEFAULT CURRENT_DATE, FOREIGN KEY (restaurant_id) REFERENCES Restaurant(restaurant_id) ); CREATE TABLE EntertainmentSuggestion ( suggestion_id INT PRIMARY KEY AUTO_INCREMENT, restaurant_id INT NOT NULL, suggestion_text TEXT NOT NULL, applicable_days VARCHAR(100), FOREIGN KEY (restaurant_id) REFERENCES Restaurant(restaurant_id) ); ``` This supports: - Multiple reviews (each with reviewer, rating, comment, date) per restaurant - Multiple entertainment suggestions per restaurant **Example insert:** ```sql INSERT INTO Restaurant (name, address, description) VALUES ('Little Four Bro', '123 Main St.', 'Famous for clear, fresh BBQ. Great for gatherings.'); INSERT INTO Review (restaurant_id, reviewer_name, rating, comment) VALUES (1, 'Alice', 5, 'The BBQ pork is the best I\'ve ever tasted!'), (1, 'Bob', 5, 'Loved their Peking duck, it was perfectly crispy.'), (1, 'Charlie', 5, 'Excellent service and elegant ambiance.'), (1, 'Diana', 5, 'Their shrimp dumplings are a must-try.'), (1, 'Edward', 5, 'Authentic flavors and generous portions.'); INSERT INTO EntertainmentSuggestion (restaurant_id, suggestion_text, applicable_days) VALUES (1, 'Waiters sometimes host live music performances on select evenings.', 'Fridays, Saturdays'); ``` Query examples available upon request. This model is easily extended for photos, tags, etc. Here’s a normalized SQL data model: ```sql CREATE TABLE Restaurant ( restaurant_id INT PRIMARY KEY AUTO_INCREMENT, name VARCHAR(100) NOT NULL, address VARCHAR(200), description TEXT ); CREATE TABLE Review ( review_id INT PRIMARY KEY AUTO_INCREMENT, restaurant_id INT NOT NULL, reviewer_name VARCHAR(100) NOT NULL, rating DECIMAL(2,1) NOT NULL, comment TEXT, review_date DATE DEFAULT CURRENT_DATE, FOREIGN KEY (restaurant_id) REFERENCES Restaurant(restaurant_id) ); CREATE TABLE EntertainmentSuggestion ( suggestion_id INT PRIMARY KEY AUTO_INCREMENT, restaurant_id INT NOT NULL, suggestion_text TEXT NOT NULL, applicable_days VARCHAR(100), FOREIGN KEY (restaurant_id) REFERENCES Restaurant(restaurant_id) ); ``` With this, every restaurant can have multiple reviews and entertainment suggestions. For example: ```sql INSERT INTO Restaurant (name, address, description) VALUES ('Little Four Bro', '123 Main St.', '清新而有张力的烧腊，环境优雅，非常适合聚餐'); INSERT INTO Review (restaurant_id, reviewer_name, rating, comment) VALUES (1, 'Alice', 5, 'The BBQ pork is the best I\'ve ever tasted!'), (1, 'Bob', 5, 'Loved their Peking duck, it was perfectly crispy.'), (1, 'Charlie', 5, 'Excellent service and elegant ambiance.'), (1, 'Diana', 5, 'Their shrimp dumplings are a must-try.'), (1, 'Edward', 5, 'Authentic flavors and generous portions.'); INSERT INTO EntertainmentSuggestion (restaurant_id, suggestion_text, applicable_days) VALUES (1, 'Waiters sometimes host live music performances on select evenings.', 'Fridays, Saturdays'); ``` You can easily join these tables to get all info for each establishment. Here’s a robust SQL data model supporting detailed restaurant reviews, customer comments, and associated entertainment suggestions. This model allows multiple reviews per restaurant, stores reviewer names/ratings/comments, and attaches multiple entertainment entries to each restaurant. --- ### **Schema** #### 1. **Restaurant Table** Stores the basic info about each restaurant. ```sql CREATE TABLE Restaurant ( restaurant_id INT PRIMARY KEY AUTO_INCREMENT, name VARCHAR(255) NOT NULL, address VARCHAR(255), description TEXT ); ``` #### 2. **Review Table** Each record is a customer review for a particular restaurant. ```sql CREATE TABLE Review ( review_id INT PRIMARY KEY AUTO_INCREMENT, restaurant_id INT NOT NULL, customer_name VARCHAR(100), -- Optionally link to a Customer table if desired rating DECIMAL(2,1) NOT NULL, -- e.g. 4.5 comment TEXT, review_date DATE DEFAULT CURRENT_DATE, FOREIGN KEY (restaurant_id) REFERENCES Restaurant(restaurant_id) ); ``` #### 3. **EntertainmentSuggestion Table** Holds entertainment suggestions/specials for each restaurant. ```sql CREATE TABLE EntertainmentSuggestion ( suggestion_id INT PRIMARY KEY AUTO_INCREMENT, restaurant_id INT NOT NULL, suggestion_text TEXT NOT NULL, applicable_days VARCHAR(100), -- e.g. "Every Friday" FOREIGN KEY (restaurant_id) REFERENCES Restaurant(restaurant_id) ); ``` --- ### **Sample Inserts** ```sql -- Add restaurant INSERT INTO Restaurant (name, address, description) VALUES ('Little Four Bro', '123 Main St.', '清新而有张力的烧腊，环境优雅，非常适合聚餐'); -- Add reviews INSERT INTO Review (restaurant_id, customer_name, rating, comment) VALUES (1, 'Alice', 5, 'The BBQ pork is the best I\'ve ever tasted!'), (1, 'Bob', 5, 'Loved their Peking duck, it was perfectly crispy.'), (1, 'Charlie', 5, 'Excellent service and elegant ambiance.'), (1, 'Diana', 5, 'Their shrimp dumplings are a must-try.'), (1, 'Edward', 5, 'Authentic flavors and generous portions.'); -- Add entertainment suggestion INSERT INTO EntertainmentSuggestion (restaurant_id, suggestion_text, applicable_days) VALUES (1, 'Waiters sometimes host live music performances on select evenings.', 'Fridays & Saturdays'); ``` --- ### **Example Query** Fetch all reviews and any entertainment suggestions for "Little Four Bro": ```sql SELECT r.name AS restaurant, rv.customer_name, rv.rating, rv.comment, es.suggestion_text, es.applicable_days FROM Restaurant r LEFT JOIN Review rv ON r.restaurant_id = rv.restaurant_id LEFT JOIN EntertainmentSuggestion es ON r.restaurant_id = es.restaurant_id WHERE r.name = 'Little Four Bro'; ``` --- ### **Notes** - You can easily expand this model—for example, add a `Customer` table and link `review.customer_name` to a customer’s id. - The model accommodates as many reviews/comments per restaurant as you wish. - Entertainment suggestions are decoupled and allow for multiple entries per restaurant. This structure should serve your needs for managing multi-review, comment-enabled restaurant information, along with supporting entertainment suggestions. Let me know if you want customization for additional features!