How rigo-godoy/proyecto-final-bdd works
This is a console-based medical patient manager. The main workflow accepts patient details or an operation from the user, coordinates patient CRUD through a DAO, and accesses MariaDB over JDBC. The documented SQL setup also defines the wider Patients–Appointments–Payments schema and optional stored procedures for daily sales, current patients, and patient insertion; these are distinct from the Java menu. The source excerpts support the Java calls and schema relationships, but do not show the SQL script contents directly.
Main entry points: PacienteDAO.java Patient CRUD · Main.java Menu coordinator · appHospital.sql Hospital schema · pl_sql.sql Stored procedures
Components 8
Console workflow
- Menu coordinator
src/main/java/Proyecto_Final_bdd/Main.java
Patient operations
- Patient model
src/main/java/Proyecto_Final_bdd/Paciente.java - Patient CRUD
src/main/java/Proyecto_Final_bdd/PacienteDAO.java
Database access
- JDBC connection
src/main/java/Proyecto_Final_bdd/ConexionSQL.java - MariaDB
SQL capabilities
- Hospital schema
appHospital.sql - Stored procedures
pl_sql.sql
Other components
- Console user
Connections 10
- Console user → Menu coordinator: enters choices
src/main/java/Proyecto_Final_bdd/Main.java - Menu coordinator → Patient CRUD: dispatches CRUD
src/main/java/Proyecto_Final_bdd/Main.java - Menu coordinator → Patient model: builds patient
src/main/java/Proyecto_Final_bdd/Main.java - Patient CRUD → Patient model: reads fields
src/main/java/Proyecto_Final_bdd/PacienteDAO.java - Patient CRUD → JDBC connection: opens connection
src/main/java/Proyecto_Final_bdd/PacienteDAO.java - JDBC connection → MariaDB: connects JDBC
README.md - Patient CRUD → Hospital schema: queries patients
README.md - Hospital schema → MariaDB: creates schema
README.md - Stored procedures → Hospital schema: uses tables
README.md - Stored procedures → MariaDB: defines procedures
README.md