database script completed

database.sql

@@ -1,141 +1,83 @@
--- Restaurant Database Management System
+
---
+DROP TABLE IF EXISTS order_details CASCADE;
--- Instructions:
+DROP TABLE IF EXISTS orders CASCADE;
--- 1. Create all required tables.
+DROP TABLE IF EXISTS menu_item CASCADE;
--- 2. Design appropriate PRIMARY KEY and FOREIGN KEY relationships.
+DROP TABLE IF EXISTS users CASCADE;
--- 3. Add suitable constraints based on the requirements.
--- 4. Insert initial mock data.
--- 5. Insert at least 3 menu items.
--- 6. The script should be executable from start to finish without errors.
 
 
-
+CREATE TABLE users (
--- =======================================================
+                       uid SERIAL PRIMARY KEY,
--- USER TABLE
+                       username VARCHAR(50) UNIQUE NOT NULL,
--- =======================================================
+                       password VARCHAR(255) NOT NULL,
---
+                       email VARCHAR(100)
--- Represents customers using the system.
+);
---
--- Required information:
--- - Unique identifier
--- - Username
--- - Password
--- - Email (optional)
---
--- Requirements:
--- - Each user must have a unique identifier.
--- - Usernames must be unique.
--- - Username and password are required.
--- - Passwords should not be stored in plain text.
---
--- CREATE TABLE ...
 
 
-
+CREATE TABLE menu_item (
--- =======================================================
+                           uid SERIAL PRIMARY KEY,
--- MENU ITEM TABLE
+                           name VARCHAR(50) NOT NULL,
--- =======================================================
+                           price DECIMAL(10, 2) NOT NULL CHECK (price > 0),
---
+                           category VARCHAR(50)
--- Represents available food and drink items.
+);
---
--- Required information:
--- - Unique identifier
--- - Name
--- - Description (optional)
--- - Price
--- - Category (optional)
---
--- Requirements:
--- - Each menu item must have a unique identifier.
--- - Name is required.
--- - Price must always be positive.
---
--- CREATE TABLE ...
 
 
+CREATE TABLE orders (
+                        uid SERIAL PRIMARY KEY,
+                        user_id INTEGER NOT NULL,
+                        order_date TIMESTAMP DEFAULT CURRENT_TIMESTAMP,
+                        total_price DECIMAL(10, 2) NOT NULL CHECK (total_price >= 0),
 
--- =======================================================
+                        CONSTRAINT fk_orders_user
--- ORDER TABLE
+                            FOREIGN KEY (user_id)
--- =======================================================
+                                REFERENCES users(uid)
---
+                                ON DELETE CASCADE
--- Represents orders placed by customers.
+);
---
--- Required information:
--- - Unique identifier
--- - Reference to customer
--- - Creation date and time
--- - Total price
---
--- Requirements:
--- - Each order must belong to exactly one user.
--- - A user can have multiple orders.
--- - The relationship between User and Order must be implemented.
---
--- Note:
--- Avoid using reserved SQL keywords as table names.
--- Consider using a name such as "orders" or "customer_orders".
---
--- CREATE TABLE ...
 
 
+CREATE TABLE order_details (
+                               uid SERIAL PRIMARY KEY,
+                               order_id INTEGER NOT NULL,
+                               item_id INTEGER NOT NULL,
+                               quantity INTEGER NOT NULL CHECK (quantity > 0),
+                               item_price DECIMAL(10, 2) NOT NULL CHECK (item_price >= 0),
 
--- =======================================================
+                               CONSTRAINT fk_order_details_order
--- ORDER DETAIL TABLE
+                                   FOREIGN KEY (order_id)
--- =======================================================
+                                       REFERENCES orders(uid)
---
+                                       ON DELETE CASCADE,
--- Represents items inside an order.
+
---
+                               CONSTRAINT fk_order_details_menu_item
--- Required information:
+                                   FOREIGN KEY (item_id)
--- - Unique identifier
+                                       REFERENCES menu_item(uid)
--- - Reference to an order
+                                       ON DELETE RESTRICT
--- - Reference to a menu item
+);
--- - Quantity
--- - Item price at purchase time
---
--- Requirements:
--- - Each detail record must belong to one order.
--- - Each detail record must reference one menu item.
--- - Quantity must always be greater than zero.
--- - Store the item's price at the moment of purchase.
---
--- CREATE TABLE ...
 
 
-
+INSERT INTO menu_item (name, price, category) VALUES
--- =======================================================
+                                                  ('French Fries', 1.00, 'Appetizer'),
--- INITIAL MENU DATA
+                                                  ('Chicken Burger', 4.05, 'Burger'),
--- =======================================================
+                                                  ('Pepperoni Pizza', 8.39, 'Pizza'),
---
+                                                  ('Milkshake', 2.20, 'Drink'),
--- Insert at least 3 food or drink items.
+                                                  ('Ravioli', 9.00, 'Pasta');
---
--- Example categories:
--- - Pizza
--- - Burger
--- - Pasta
--- - Drink
---
--- INSERT INTO ...
 
 
-
+INSERT INTO users (username, password, email) VALUES
--- =======================================================
+                                                  ('saraz', '8d969eef6ecad3c29a3a629280e686cf0c3f5d5a86aff3ca12020c923adc6c92', 'sarrr@gmail.com'),
--- OPTIONAL TEST DATA
+                                                  ('kave02', '8d969eef6ecad3c29a3a629280e686cf0c3f5d5a86aff3ca12020c923adc6c92', 'kaviii02@gmail.com'),
--- =======================================================
+                                                  ('titami_t', '8d969eef6ecad3c29a3a629280e686cf0c3f5d5a86aff3ca12020c923adc6c92', 'titaza@gmil.com');
---
--- You may insert sample users and orders for testing.
--- This section is optional.
---
--- INSERT INTO ...
 
 
+INSERT INTO orders (user_id, order_date, total_price) VALUES
+                                                          (1, CURRENT_TIMESTAMP, 9.39),
+                                                          (2, CURRENT_TIMESTAMP, 13.05),
+                                                          (1, CURRENT_TIMESTAMP, 2.20),
+                                                          (3, CURRENT_TIMESTAMP, 8.39);
 
--- =======================================================
+
--- VERIFICATION QUERIES
+INSERT INTO order_details (order_id, item_id, quantity, item_price) VALUES
--- =======================================================
+                                                                        (1, 1, 1, 1.00),
---
+                                                                        (1, 3, 1, 8.39),
--- Uncomment these queries to verify your database.
+                                                                        (2, 2, 1, 4.05),
---
+                                                                        (2, 5, 1, 9.00),
--- SELECT * FROM ...;
+                                                                        (3, 4, 1, 2.20),
--- SELECT * FROM ...;
+                                                                        (4, 3, 1, 8.39);
--- SELECT * FROM ...;
--- SELECT * FROM ...;