Computer Science BS Journal (CST363) : Week 6

 This week I learned quite a bit about JDBC, Connectors, and what it takes to work on some Web Applications. 

*JDBC is the standard Java API for connecting and executing SQL queries with relational databases.

  • Key Concepts:

    • DriverManager / DataSource: Manages DB connections.

    • Connection: Represents a connection session.

    • PreparedStatement: Safely sends parameterized SQL (prevents SQL injection).

    • ResultSet: Retrieves query results.

    Some key takeaways:

    • Use PreparedStatement for safe, efficient, and secure database queries.

    • Always close connections (or use try-with-resources).

    • Avoid hardcoding SQL logic — parameterize everything.

    • Use jdbcTemplate.getDataSource().getConnection() in Spring Boot for quick integration.

*Spring Boot simplifies JDBC usage by handling connection setup and dependency injection through JdbcTemplate.

Key Concepts:

  • @Autowired JdbcTemplate gives access to your DB.

  • Spring Boot reads config from application. Properties (e.g., DB URL, user/pass).

  • DAO (Data Access Object) pattern is often used for cleaner DB logic.

Takeaways:

  • JdbcTemplate abstracts repetitive JDBC code and handles connection pooling.

  • Connection pooling improves performance in web apps.

  • Errors are easier to manage using try-catch around getConnection() or Spring’s exception handling.


What we built(Web Application Lab 18/19):

  • A multi-page Spring Boot web app to manage doctors, patients, prescriptions, pharmacies, and fills.

  • Used forms to:

    • Register and update users.

    • Create and fill prescriptions.

    • Validate and persist data in a MySQL database.

Key Concepts:

  • @Controller classes map URL routes to methods.

  • Model objects pass data from backend to templates.

  • Thymeleaf (via .html templates) renders dynamic views.

  • Forms submit data via @PostMapping to controller methods.

Takeaways:

  • MVC (Model-View-Controller) structure keeps code organized.

  • Views should never trust user input — always validate and cross-check in controller logic.

  • JDBC + Web = full CRUD (Create, Read, Update, Delete) system when properly connected.



Comments

Post a Comment

Popular posts from this blog

Computer Science BS Journal: Week 4

  Part One: Set Your Educational Goals  Something I want to achieve by the end of this CS program at Monterey Bay is to have a portfolio full of projects. We learned in the recent weeks that a portfolio is more important than a resume for a programmer and I stand by that. I would like to have several large scale projects completed with my group and perhaps a few solo projects in said portfolio so I may display all that I have learned. My goal? Port-Fillio (Fill out my portfolio). Part Two: Set Your Career Goals      It may not seem like much but my career goals are sort of simple. I want to be a full-stack developer, the company I work for does not matter to me so much as the work-life balance. Traveling is very important to me so a remote job that gives me the freedom to move around is a must. I envision myself with my significant other putting in our hours and then going out to explore a new country we just landed in. This lifestyle has already been attained b...
Read more

Computer Science BS Journal: Week 2

Image
                                               Part 1: Review and Reflect Learning Strategy The Effective Study Skills google document goes into detail that every person is different when it comes to studying and retaining knowledge. Key tips and tricks that are proven to help with your studies are highlighted throughout the document which bring insight into how you should prepare yourself for a study session and how you should conduct your studies. Poor study skills are wasted time, and wasted time leads to frustration and low grades. From the document I can say that the top 3 things highlighted that I am already good at are scheduling, extracting important details, and reviewing and revising. On the other hand the top 3 things I feel that I need to work on are taking notes, taking examinations and gathering materials when I write. I tend to review...
Read more

Computer Science BS Journal: Week 5

Image
Post Interview Reflection Report Introduction : Who you interview and why. The expert’s name, title, and organization. A brief background on why you selected this person. I interviewed Joshua Brackett, he's been a close friend of mine for going on 8 years and he works in the same industry I'm looking to transition into. Joshua is a Customer Success Engineer working at Zipline. I decided to interview Joshua because as I mentioned, he's a close friend of mine and I felt it would be a more meaningful interview asking him directly. During the interview I felt like the information and tips I was getting was directed at me and not just a broad overview of his industry/job. Summary : Key takeaways from the conversation (e.g., career advice, insights into industry trends, technical challenges). Some key takeaways I got from the conversation was that a) your portfolio means a lot when you're looking for a job, technical knowledge is important for the interview process but they a...
Read more