Faith Thomas

Briefly summarize what you consider to be the three most important things you learned in this course. 1. I learned how to design a database using entities, relationships, and attributes. I could apply this to building an ER diagram in mySQL. This helped me to understand structure of databases and how thy connect. 2. I learned how to use SQL to create tables and insert data by using commands like select, join, and group by. Querying data helped me learn that databases are good tools for not only organizing but also analyzing data.  3. I learned that normalization is important. It taught me about constraints like pks, fks, and even how transactions keep the data reliable and accurate. 

Compare MongoDB with MySQL What are some similarities?  MySQL and mongoDB are both databases used to store and manage information. You can add, read, update, and delete data. They both use indexes to make searches faster and include security features to protect data. They also allow developers to connect from different programming languages like Java. Overall they both help organize and access data for applications. What are some differences?  I think mySQL and mongoDB are different in how they store and organize data. MySQL uses tables with rows and columns, while mongoDB uses documents that look like JSON files. MySQL has a fixed structure but mongoDB can store data that changes or doesn’t always follow the same format. Also mySQL is better for data that needs strong relationships and rules, while mongoDB is better for data that needs to grow and change quickly. When would you choose one over the other? I would choose mySQL when data is organized, consistent, and needs stron...

  Summarize what you have learned this week This past week, I learned how programming languages connect and interact with databases. I read on zybooks how SQL can be embedded into languages like C and how APIs like JDBC allow communication between programs and databases. I also practiced working with database connections. My teammates and I worked on a group project where we built a database and connected it to a local server using MySQL Workbench. We wrote Java code to run and test the connection, add data, and verify that everything worked properly. It was about completing a web application for a prescription database that connects to a MySQL database. It lets users register doctors and patients, create and fill prescriptions, and update records through a web interface powered by Spring Boot and Java , while the data is stored and managed in MySQL Workbench . It was fun collaborating and seeing how the concepts we learned in class applied to a real project. 

The web site   "Use the Index Luke"  has a page on "slow indexes".    https://use-the-index-luke.com/sql/anatomy/slow-indexes Links to an external site. If indexes are supposed to speed up performance of query,  what does the author mean by a slow index?   Even though the database is using an index, the query can still take a long time to run, making it a "slow index". If the database has to look through a lot of matching entries in the index then get each row from the table it can take extra time because slows down  the performance . The process of following all the matches and getting the data can make it slower than expected.