3rd Week in 363 Database Management

 

  1. What is an SQL view.  How is it similar to a table? In what ways is it different (think about primary keys,  insert, update, delete operations) 
    1. SQL views are like tables in that they display a restructured table columns and data types, they both contain table data just that a view is more like a virtual table.  The differences between a view an a table is that views might have issues using insert, update, and delete statements. Since primary keys from a base might not be in a view during an insert a primary key can not be null there for it is not allowed. Aggregate values in a view might be used and update or insert to the view might create a new aggerate value which the must be converted to many base tables and the conversion is undefined there for that is also restricted. 

  1. We have completed our study of SQL for this course.  This is not to imply that we have studied everything in the language.  There are many specialized features such as calculating rolling averages, query of spatial data (data with latitude and longitude) coordinates, and more. But take a minute to think about how SQL compares to other programming languages such as Java.  What features are similar , and which are present in one language but not in the other?  For example,  Java has conditional if statements which are similar to SQL WHERE predicates,  the SELECT clause is similar to a RETURN statement in that it specifies what data or expression values are to be returned in the query result (although it is strange that a statement should specify the RETURN as the first part of a SELECT. 
    1. Well in some ways there is similar syntax as with "()" means some type of function in both java and SQL. There are closing ";" end statements. There are built in functions such as avg() with is similar to have java has some built in functions. Some different features are like how data is manipulated or joined together using Join, union, group by while java focus on objects and algorithms. 

Comments

Post a Comment

Popular posts from this blog

CST438 Software Engineering: Week 8 (Final week)

 One of the most important things I learned is that software engineering is about much more than just writing code. While coding is a big part, there's a strong emphasis on documentation, understanding client needs, and getting continuous feedback. It’s about designing systems so others can easily improve them and applying principles like "low coupling and high cohesion" to keep things modular and maintainable.      Another key lesson was understanding the entire development process from end to end. This was the first time I worked with both the front end and back end together, fully grasping the HTTP protocol (including how methods like POST work), how JSON is used, and how the front end communicates with the back end. Seeing how everything fits from database interactions to deploying the app online—gave me a fascinating glimpse into the full workflow and a lot of practical experience.      Another important lesson was learning how to work as part of ...
Read more

CST438 Software Engineering: Week 1

What did you expect a course in Software Engineering would cover? I expected it to cover how to build applications from the ground up and the design behind application development. I thought we would look at other things we’ve been learning in this program, like database management, front end development, and back end work, and then put it all together into one complete project. After completing week 1, how has your opinion changed? Well, I never really thought much about keeping an application’s design maintainable for future improvements or changes. There is a lot more that goes into software engineering than just simple programming. It is  about planning ahead, documenting your work, checking for errors, and testing properly to avoid issues later. I’ve also realized software engineering looks at the big picture it is not just about coding and design but about how software impacts people and how teams work together to build it. Developers need to stay motivated, think critical...
Read more

CST370 Week 5

Hello everyone,  This week we studied binary‑tree traversals preorder, inorder, and postorder but I kept mixing them up. I finally got it when I attended TA office hours, and it clicked. Walking through Quick Sort step by step helped me see how the Decrease and Conquer approach works by breaking problems into smaller chunks. Then we looked at Kahn’s algorithm, and watching it remove nodes with no incoming edges reminded me of picking a pivot in Quick Sort. Seeing these patterns repeat helped me realize that many algorithms work by simplifying things piece by piece. 
Read more