Cohort 23 CS Online Journal

(Mobile format, bear with me!) The three most important things that I've learned in this course are: - Understanding how ER diagrams work, how to create one from a client's story, and how to translate them into a database of choice. How to use a DBMS is good, but the fundamentals of translating a story into an ER diagram can apply to many more situations. - Knowing different types of DBMS and their uses. Traditional (transactional) databases like MySQL are good for managing in-house data for a moderately small business or similar. NoSQL databases that manage big data like MongoDB are useful for managing high volumes of it in a timely manner. Database design is dependent on what DBMS is used. - Gaining experience with MySQL. MySQL is a traditional database that uses the SQL language to create queries. While simple to begin with, it can become much more complex with nested queries. I would want to practice more with nested queries because it is still confusing for me.

Learning Journal Week 7      MongoDB and MySQL are two types of database - MongoDB is a document database that utilizes NoSQL practices, while MySQL is a relational database that uses tables. They are similar in that they can both store large amounts of data and retrieve them reliably, if created correctly. Their main difference is what kind of data is stored in them - MySQL databases are better at handling transactional data, while MongoDB databases can manage big data more efficiently than traditional SQL databases like MySQL.       If I were to use a database for a project, I would most likely use MySQL for it. I do not believe I need any data properties that are exclusive to big data, so having more control over the database's environment using MySQL would be ideal.       If I were to create a different project for some sort of social network, I would use MongoDB over MySQL. Social network data tends to have big data properties,...

Week 6 Learning Journal      This week, I learned a lot more about how JDBC works and how to connect a java program to a MYSQL database. This week's group project was easy to understand, and while I had some difficulty with a few implementations, my teammates were able to figure out what went wrong and explained to me what to do instead. Thanks team!

Use the Index, Luke      This title references the website:   Use the index, Luke      A "slow index" in this case is an index range scan that is looking through a majority of an index, causing it to access tables many times more than what could be necessary. One solution to this problem is to write better `where` clauses for search queries. The author also mentions specific "anti-patterns" to avoid, which include mixing data types (like using numbers exclusively in a string), math in search queries, and using date types incorrectly.