feat: database.sql

This commit is contained in:
2026-06-29 21:13:09 +03:30
parent 00f990c653
commit fc297103fa
2 changed files with 34 additions and 120 deletions
+2
View File
@@ -2,6 +2,8 @@
# Compiled class file # Compiled class file
*.class *.class
.idea/
# Log file # Log file
*.log *.log
+32 -120
View File
@@ -1,141 +1,53 @@
-- Restaurant Database Management System -- Restaurant Database Management System
--
-- Instructions:
-- 1. Create all required tables.
-- 2. Design appropriate PRIMARY KEY and FOREIGN KEY relationships.
-- 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.
-- ======================================================= -- =======================================================
-- USER TABLE -- USER TABLE
-- ======================================================= -- =======================================================
-- CREATE TABLE users (
-- Represents customers using the system. id SERIAL PRIMARY KEY,
-- username VARCHAR(50) NOT NULL UNIQUE,
-- Required information: password_hash VARCHAR(255) NOT NULL,
-- - Unique identifier email VARCHAR(100)
-- - 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 ...
-- ======================================================= -- =======================================================
-- MENU ITEM TABLE -- MENU ITEM TABLE
-- ======================================================= -- =======================================================
-- CREATE TABLE menu_items (
-- Represents available food and drink items. id SERIAL PRIMARY KEY,
-- name VARCHAR(100) NOT NULL,
-- Required information: description TEXT,
-- - Unique identifier price NUMERIC(10, 2) NOT NULL CHECK (price > 0),
-- - Name category VARCHAR(50)
-- - Description (optional) );
-- - Price
-- - Category (optional)
--
-- Requirements:
-- - Each menu item must have a unique identifier.
-- - Name is required.
-- - Price must always be positive.
--
-- CREATE TABLE ...
-- ======================================================= -- =======================================================
-- ORDER TABLE -- ORDER TABLE
-- ======================================================= -- =======================================================
-- CREATE TABLE orders (
-- Represents orders placed by customers. id SERIAL PRIMARY KEY,
-- user_id INT NOT NULL REFERENCES users(id) ON DELETE CASCADE,
-- Required information: created_at TIMESTAMP NOT NULL DEFAULT NOW(),
-- - Unique identifier total_price NUMERIC(10, 2) NOT NULL CHECK (total_price >= 0)
-- - 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 ...
-- ======================================================= -- =======================================================
-- ORDER DETAIL TABLE -- ORDER DETAIL TABLE
-- ======================================================= -- =======================================================
-- CREATE TABLE order_details (
-- Represents items inside an order. id SERIAL PRIMARY KEY,
-- order_id INT NOT NULL REFERENCES orders(id) ON DELETE CASCADE,
-- Required information: menu_item_id INT NOT NULL REFERENCES menu_items(id),
-- - Unique identifier quantity INT NOT NULL CHECK (quantity > 0),
-- - Reference to an order unit_price NUMERIC(10, 2) NOT NULL CHECK (unit_price > 0)
-- - 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 ...
-- ======================================================= -- =======================================================
-- INITIAL MENU DATA -- INITIAL MENU DATA
-- ======================================================= -- =======================================================
-- INSERT INTO menu_items (name, description, price, category) VALUES
-- Insert at least 3 food or drink items. ('Margherita Pizza', 'Classic tomato sauce and mozzarella', 10.00, 'Pizza'),
-- ('BBQ Burger', 'Juicy beef patty with BBQ sauce', 8.50, 'Burger'),
-- Example categories: ('Spaghetti Carbonara', 'Creamy pasta with pancetta and egg', 12.00, 'Pasta'),
-- - Pizza ('Tiramisu', 'Italian coffee dessert', 5.50, 'Dessert'),
-- - Burger ('Cola', 'Ice-cold soft drink', 2.50, 'Drink');
-- - Pasta
-- - Drink
--
-- INSERT INTO ...
-- =======================================================
-- OPTIONAL TEST DATA
-- =======================================================
--
-- You may insert sample users and orders for testing.
-- This section is optional.
--
-- INSERT INTO ...
-- =======================================================
-- VERIFICATION QUERIES
-- =======================================================
--
-- Uncomment these queries to verify your database.
--
-- SELECT * FROM ...;
-- SELECT * FROM ...;
-- SELECT * FROM ...;
-- SELECT * FROM ...;