Week 20: CST363 3rd week!

    This week, we covered Chapter 5 and completed our first exam for the course. One of the topics we explored was SQL views. A view functions like a table in terms of querying,  but there are some differences. For instance, views typically don’t have primary keys and can restrict certain operations like insert, update, or delete unless specific conditions are met. This makes views useful for simplifying complex queries or securing data, but they behave differently from traditional tables in terms of data modification.

When I think about how SQL stacks up against other languages like Java, I wouldn't exactly call them two peas in a pod. Sure, they both have their ways of handling data and making decisions, but their core purposes are worlds apart.

Think of it like this: SQL is the master of the database domain. It's all about talking directly to the database, pulling out the exact information you need. Java, on the other hand, is more like a versatile toolbox. It can build all sorts of applications, and sometimes that includes chatting with databases using special libraries.

So, while they both use things like IF/ELSE statements (or WHERE clauses in SQL) to make choices, and they can both store and crunch numbers with variables and expressions, they're really built for different jobs. SQL is laser-focused on databases, while Java is ready to tackle a whole range of programming tasks.