This week in SQLand, I learned how to code subqueries, create databases, and work with some of SQL's more complex functionality over the base functions from last week.
Subqueries are tricky, and can get complicated pretty quickly in certain situations. However, they are quite powerful because they allow the user to filter results to a finer degree than pure table joins with single "ON" conditions. I can already see myself using subqueries for our upcoming group project.
I also learned about the levels of database normalization, and how to improve database efficiency and reduce data redundancy through good database design. I feel as if this is the most important part of SQL, and database programming in general - without a well designed or maintainable database, applications that rely on querying data (e.g. almost everything) are quite limited in their functionality, or in the worst case don't work at all. Lastly, the different of levels of normalization can significantly determine database efficiency, which is another point this week's assigned readings covered.
Lastly, I learned how to construct an E-R diagram through reverse engineering, and how to interpret these diagrams. E-R diagrams show the relationships between tables designated as primary and foreign keys, and they give a clear overview of how tables in a database are related to each other. As a visual learner, I find these diagrams interesting and useful. Data visualization is a subject where researchers and programmers alike are searching for new ways or more efficient ways to display data, and I think E-R diagrams are a nice example of it.
Subqueries are tricky, and can get complicated pretty quickly in certain situations. However, they are quite powerful because they allow the user to filter results to a finer degree than pure table joins with single "ON" conditions. I can already see myself using subqueries for our upcoming group project.
I also learned about the levels of database normalization, and how to improve database efficiency and reduce data redundancy through good database design. I feel as if this is the most important part of SQL, and database programming in general - without a well designed or maintainable database, applications that rely on querying data (e.g. almost everything) are quite limited in their functionality, or in the worst case don't work at all. Lastly, the different of levels of normalization can significantly determine database efficiency, which is another point this week's assigned readings covered.
Lastly, I learned how to construct an E-R diagram through reverse engineering, and how to interpret these diagrams. E-R diagrams show the relationships between tables designated as primary and foreign keys, and they give a clear overview of how tables in a database are related to each other. As a visual learner, I find these diagrams interesting and useful. Data visualization is a subject where researchers and programmers alike are searching for new ways or more efficient ways to display data, and I think E-R diagrams are a nice example of it.
Comments
Post a Comment