Tuesday, January 31, 2017

CST 363 Week 4

CST 363 Week 4

This week we delved deeper into the design process of database building. I learned about the process of looking for entities is very similar to the process of looking for objects in standard programming. You must look for the nouns that could be entities in the data model. I learned about the difference in weak vs strong entities, how the representation of a weak entity differs from that of a strong entity. The various types of keys where explored and when it is necessary to use them. The concept of referential integrity was learned about when implementing foreign keys in a design.

We then learned about how to create an E-R diagram in MySQL Workbench and how to forward engineer it into a functional .sql script. Conversely, I learned how to reverse engineer a . sql script into an E-R diagram. Through the building of E-R diagrams, I also learned about the implementation of subtypes in database design.

The next step in the design process is the normalize the tables. Without normalization, the tables can experience modification problems. It was also discussed the after normalization comes denormalization as sometimes the process of normalizing can go to far and negatively affect the design of the database.

Tuesday, January 24, 2017

CST 363 Week 3

CST 363 Week 3

This week I learned more SQL statements and how they relate to other coding functions. I learned about SQL grouping, outer join and sub-selects operations.  I was able to comprehend how a SQL select statement is similar to a loop through an array. I also learned about the various aggregate functions SQL uses such as COUNT(), MIN(), MAX(), SUM(), and AVG(). I am now able to differentiate on when to use a cartesian product join or inner join, a left outer join, and a right outer join. I learned that a subquery is like the inner loop of a nested loop control structure in programming. It is important to know that a DBMS is better at optimizing join operations when compared to subquery operations.

I took my first exam for the course which I felt adequately tested my knowledge on what has been learned so far. Again, practice, practice, practice is how I will get better.

On a side note, I was accepted to volunteer at the Game Developer's Conference and start my path in gaining contacts in the game development industry. I am excited for the opportunity that this will afford me in gaining knowledge on how to better myself to enter this industry.

Tuesday, January 17, 2017

CST 363 Week 2

CST 363 Week 2

This week I learned about implement SQL and php statements into HTML forms to be able to implement them in web pages. This was a bit of a crash course in HTML as I have only briefly touched on the subject. I learned about the basics of creating an HTML webpage and how to implement php files inside of them. I like how this showed a real world application of using SQL and php.
I also got a refresher on the various data structures that are used in databases such as linked lists and indexes. It was good to refresh my memory on the various indexes such as B-Tree index and Hash index and when it is good to implement each.
It is evident that a lot more practice will be needed in order to be proficient at writing php statements to be implemented in HTML as I have only scratched the surface. This week has laid a good foundation on which to build upon.
I found it uplifting that I was able to help a classmate out on getting the ball rolling with assignment 3.

Tuesday, January 10, 2017

CST 363 Week 1

CST 363 Week 1

This week I began my Introduction to Database Systems class!!!

I began this class not knowing a thing about SQL language. I found it to be extremely logical in its iterations. Although vastly different than C++, Java, or Python, I found it easy to identify the flow of logic used in creating expressions.

This week I learned how to create a schema in MySQL and run a script to add tables to the schema. I also learned how to select, update, add, and remove data from a database using SQL commands. I look forward to seeing what the next 8 weeks have in store for learning about Database Systems.