How manoeltelesps/database_projects works
Project Type and Purpose
• This is a collection of database‐centric exercises and practical SQL scripts (MySQL) for learning and experimenting with data modeling and manipulation.
• There is no frontend or application server—your system “understanding” revolves around SQL script files, the database engine, and the resulting schemas.
Main Components
a. Development Environment
• A developer machine or container where scripts are authored and executed.
• Version control (Git) as an external service.
b. SQL Script Repositories
• “Atividades” folder: DDL scripts to create databases and tables.
• “Aulas/aula_1” and “Aulas/aula_2” folders: Additional schema definitions and data‐manipulation scripts.
c. Database Engine
• MySQL (or another target engine) that executes the scripts and hosts the schemas.
d. Resulting Database Schemas
• Tables (e.g., bibliotecabd, Livraria) with their relationships, primary/foreign keys.
Relationships and Data Flow
• Script files → (execute) → Database Engine
• Database Engine → (manages) → Physical tables, constraints, indexes
• Developer ↔ (Git push/pull) ↔ Git repository
Key Architectural Patterns & Principles
• Separation of concerns: scripts are organized by exercise type (Atividades vs. Aulas).
• Idempotent DDL: each script should cleanly create or alter schemas.
• Versioning: all SQL artefacts under Git for reproducibility.
Step‐by‐Step for the Principal Software Engineer
2. Drill down into MySQL: show schemas and tables created by Atividades and Aulas scripts.
3. For each script grouping: include an ERD showing table structure & relationships.