How thiagofernandesfelipe/servicos_farmaceuticos works
Project type and purpose
• This is a desktop application built with Delphi (Pascal) following a classical MVC (Model-View-Controller) pattern.
• Its purpose is to manage “Serviços Farmacêuticos,” interacting with a MySQL database (script.sql provides the schema).
• Key indicators: directories named Controllers, DAO, Models, Views; .dpr and .dproj Delphi project files; MySQL mentioned in README.
File structure
• Controllers: business-logic layer (uConexaoControl, uProcedimentoControl, uServicoControl)
• DAO: persistence layer interacting with MySQL (uConexaoDAO, uProcedimentoDAO, uServicoDAO)
• Models: data entities (uAcaoModel, uProcedimentoModel, uServicoModel)
• Views: VCL form files (.dfm + .pas) for UI (Main form and Serviços form)
• Root files: servicos_farmaceuticos.dpr (entry point), script.sql (DB schema), .res for resources
• Win32/Debug: compiled units and the .exe for local deployment/testing
README for additional insights
• Confirms MVC pattern and tech stack: Delphi 11 + MySQL 8.0.
• Suggests there are no external microservices—just a single Delphi client connecting to MySQL.
Elements
• “Views” (uFrmPrincipalView, uFrmServicoView)
• “Controllers” (uConexaoControl, uProcedimentoControl, uServicoControl)
• “Models” (uAcaoModel, uProcedimentoModel, uServicoModel)
• “DAO” (uConexaoDAO, uProcedimentoDAO, uServicoDAO)
• “MySQL Database” (tables created by script.sql)
• UI → Controller → DAO → Database
• Database → DAO → Controller → UI
• Business logic (Controllers) in another (e.g., green)
• Data layer (Models + DAO) in a third (e.g., yellow)