How ddhruvin/myretaildb works
Project type and purpose
• This is a single-component database project: a MySQL schema dump (retail.sql) plus a README explaining how to restore and query a “retail” database.
• It contains table definitions (employees, customers, products, orders), sample data, stored procedures, triggers, and example queries to analyze sales and enforce business rules.
File structure
• Top level:
• LICENSE
• README.md → contains restore instructions, sample outputs, query use cases, trigger/procedure descriptions
• retail.sql → full DDL/DML, triggers, stored-procedure code
• No frontend/backend code; the “application” is entirely in the database.
README for additional insights
• Explains:
• Tables and expected query outputs
• Stored procedure: inserts a new order and updates stock
• Trigger: prevents stock going negative
• Sample analytical queries (total revenue, top product, etc.)
• Restoration steps via CLI or Workbench
Elements
• Clear labels:
• Components (Client CLI/Workbench, MySQL Server, Retail DB)
• Tables with PK/FK relationships
• Stored Procedure and Trigger blocks
• From client tools to server (SQL commands)
• From stored procedure to tables it modifies
• From trigger to table it enforces
• Rectangles for tables (e.g., blue)
• Ovals for procedures (e.g., green)
• Diamonds for triggers (e.g., orange)