CST 363 - Week 4 - Halfway through!

What have I learned in this quick tour through SQL:

1. Generating EER documents using a SQL Script via MySQL workbench is extremely slick. It actually beats using a drawing program by A LOT.

2. SQL is very functional, being able to run a query and get a deterministic result is very nice. This compared to writing Javascript and dealing with async operations is great.

3. A SQL view is extremely powerful if you want to work with large sets of data. Being able to "hide" complex queries in simple views seems like it would be extremely useful if you're working at scale and with a team.

4. NULL in SQL is weird. Well not weird, but different from Javascript where null is more of a value. In SQL NULL being a state is definitely something that is odd.

5. SQL executes in a way I don't understand. It's not looping through data, instead it's operating on multiple data sets simultaneously. The nature of this is how its so fast, but it's quite a mind-bending concept to think through especially when we've been considering things like loops (for and while) in our other programming classes.

Questions I still have:

1. What happens when a table gets TOO big. How can I make a query faster, or more importantly diagnose why one is too slow?

2. What are the differences between all the SQL products out there. MySQL vs PostgreSQL etc ... why are they different and why are some better than others.

3. I assume we'll jump into this next week, but very curious to understand the difference between SQL and No SQL architectures.


Comments

Popular posts from this blog

CST 300 - Week 2 - More than just a draft

CST 300 - Week 5 - Capstone and More

CST 300 - Week 4 - Writing With Purpose