Learning Journal Week 6- CST363

I finished the Lab 18 peer reviews and focused on whether each ER diagram actually supports the prescription workflow. The strongest designs kept prescriptions separate from fills and stored drug prices in a way that preserves history, which makes reporting and auditing sane. I flagged fixes like using IDs for foreign keys instead of names, adding required attributes such as a pharmacy phone, and tightening a few relationship cardinalities so the rules are explicit. I also looked for basic normalization slips and confirmed that the chosen keys would prevent duplicate patients, doctors, and fills. The point was not the diagram aesthetics but whether constraints and keys would keep real data clean and predictable over time.

I also moved from Workbench queries to JDBC inside a small Spring MVC app and got comfortable with the essentials. I bind inputs with prepared statements, remember that parameters are 1 based, iterate result sets cleanly, handle NULLs correctly using wasNull for primitives, and read generated keys after inserts. For multi step changes I disable auto commit and commit or roll back on purpose, and I rely on try with resources so connections and statements close without drama. In Spring, controllers map GET to show pages and POST to process forms, pass a simple model to templates, and surface validation or constraint errors without losing user input. I tested the doctor register, display, and edit flow end to end, including the unique SSN case that re shows the form with a clear message. Configuration lives in application.properties and connections come from the app data source, which kept setup straightforward. Next for the team is to converge on one final schema, implement patient and prescription controllers with the same patterns, seed minimal lookup data, and capture screenshots and DDL for the PDF.