Learning Blog

 I'm enjoying the course so far. In this course, I have learned the following: The different types of databases and their uses How to use MySQL using Workbench How to use join statements to retrieve data from multiple tables How to use views to reuse or control the use of select statements How to design databases to reduce redundancy and inconsistencies Some questions I still have: I would like to know about key differences in designing databases with different concerns (size, security, enterprise vs consumer, etc). I'm curious about any current trends in database implementations and how that's changing in real time. I would like to know how databases handle other types of data, like images, video, etc.

1. ) 3rd normal form is basically a set of guidelines used to normalize databases. At the third level, the rule is that in tables where multiple columns are part of the key, the other columns should depend on the information in all key columns. This is important because if non-key columns are related to one column in the key but not others, it suggests that some columns of the data aren't closely related. The data would be better organized in separate tables to simplify access and maintenance. 2.) A SQL view is a way to display information found in one or more tables, but in a customized way with SQL queries. Views also help with reusability when the data needs to be displayed in a way that's much different than the underlying table saved in memory, or requires complex queries.

 1.) One example where joining tables on something other than equality between keys is when another comparison needs to be considered as well. Our textbook has a good example. Suppose there is a table for students and another table for classes. We can join the two tables based on matching unique codes for classes in both tables AND another comparison to check if the student's grade is greater than the average grade for the class. An example of a query would be: SELECT Student.name  FROM Class  INNER JOIN Student  ON Student.grade > Class.average AND Student.class_id = Class.class_id 2.) I feel SQL is pretty easy to pick up due to its similarity to spoken English. Sometimes when subqueries are nested it's a bit harder to figure out where the information is coming from, but views can be an alternative to simplify the syntax.